E-commerce software · Custom software solution

Craft Kit E-commerce & Assembly Software

Every craft kit is defined as a bill of materials, and its parts are reserved when a kit is sold. Assembly runs are planned, substitutions are recorded and subscription boxes follow monthly themes. The whole is custom-made for each seller after discovery.

Discuss your requirement The business view

Product status

Custom software solution, built to your requirements

No existing GullySystem product holds kit bills of materials or box subscriptions, so the software is custom-made for each seller. A stock system at the shop can still supply component counts.

There is no published price, free trial or live demo for this solution. Scope and cost are settled in a written proposal after discovery.

Purpose and users

The aim is that selling a kit changes the stock of every part inside it. Without that, kits sell for parts that ran out weeks ago.

It does not source components or write instructions. It records what is in each kit, how many can be assembled and when boxes are due.

Buyers
Subscribers
Assembly staff
Purchasing
Owners

Modules

What is in the system.

Kit bill of materials

Each kit lists its parts, with quantities and approved substitutes.

Component stock

Parts are counted separately from finished kits.

Assembly runs

Plan and record batches of kits, drawing down components.

Instructions and access

Instructions, videos and files released to buyers with the order.

Box subscriptions

Monthly themes, cut-offs and shipping dates for subscribers.

Workflows

How the work runs through it.

Sell to assemble

An order reserves a kit’s parts, creates a job for assembly and releases when the kit is packed.

Subscription month

The month’s box is defined, parts are reserved against active subscribers and the shipment date is set.

Catalogue and product data

What each product record holds.

Kit records

Name, contents, skill level, age guidance and photographs.

Variants

Kits offered in colourways, with different parts.

Component records

Parts with supplier, cost and reorder level.

Pricing and order rules

How prices and orders are set.

Kit price

Price compared with the cost of its parts, to show margin.

Subscription plans

Monthly, quarterly and prepaid plans with their schedules.

Gift orders

A kit sent to another address with a message.

Stock and fulfilment

From stock to the doorstep.

Component reservation

Parts for sold kits are set aside.

Assembly planning

How many kits can be built from current stock, and which part limits it.

Dispatch

Boxes ship on set dates, with tracking sent to each subscriber the same day the batch leaves the packing bench.

Payments, returns and refunds

Taking money and giving it back.

Payments

One-off and recurring payments through a gateway that supports repeat billing, once confirmed.

Returns

Missing parts are replaced from stock. Built kits follow your return rule.

Pauses and cancellations

A subscriber can skip a month or stop before the next cut-off. The reservation of parts is released at once.

Admin controls and reporting

What the team can see and change.

Roles

Purchasing, assembly and owner work from separate views.

Reports

Kits that can be built now, limiting parts, subscribers by plan and cost per kit.

Integrations

What it connects to, and on what terms.

Gateway for repeat billing

Recurring charges depend on the gateway and your bank supporting them. We confirm that first.

Stock counts

Read from your counter software in a file or feed it can produce, after testing.

Carriers

Rate cards are loaded for your couriers, and a month’s subscription parcels are booked together as one batch.

Deployment

How it is set up and run.

Setup

Servers and the store are prepared in a test environment, then copied to the live one after sign-off.

Opening

A short soft launch lets staff and a few buyers find problems at low volume.

Customisation boundaries

What can change, and where the edge is.

Settings and rules

Quantities, price breaks, delivery rules and reminders are set by your team after training.

Limits of scope

Work that needs new software, such as a mobile app, is estimated separately.

Migration and training

Moving over and getting people ready.

Data load

Done in a rehearsal first and again at go-live, with totals compared each time.

Support materials

Checklists for opening and closing the day, and for handling the common exceptions.

Support scope

What support covers.

Help desk

Staff questions are answered by a person who knows your set-up.

Larger asks

A rebuild of a flow, or a link to new software, is quoted after a short discovery.

What already exists.

Wholesale and B2B Ordering Software

A price-list ordering portal for dealers and retailers, wired to stock, credit limits and dispatch.

Learn more

Services

How it gets built.

For the business side, see Software solutions for craft kits e-commerce.

Common questions

Questions about this solution.

Does it manage subscription billing itself?

No. It schedules boxes and records plans. Taking repeat payments is done by the payment provider, if it supports them.

What if one component runs out?

The system shows the kits that cannot be built and offers an approved substitute if you define one.

Can it be bought off the shelf?

No. It is custom-made, because kit parts and box schedules differ for every seller.

Requirement discussion

Talk through your commerce requirement.

Describe what you sell, where you sell it and what is slowing you down. An engineer will reply within one business day.

No obligation
A reply within one business day
Your details stay private