How to Build a Simple Order Fulfillment Workflow

Fulfillment is the work between a customer's action and a completed promise. A parcel must be packed and sent. A service request may need review, payment, scheduling, delivery, and approval. A reliable workflow makes the next responsibility visible.

Start with one trusted list and a few meaningful stages. More labels will not repair vague offers or orders scattered across inboxes.

Separate the three facts

For every order, distinguish what the customer requested, whether payment succeeded, and how far fulfillment has progressed. Paid does not mean shipped. Requested does not mean accepted. Fulfilled does not necessarily mean no refund can occur later.

Cardel Orders keeps payment and fulfillment states separate. Successful on-site Stripe Shop purchases arrive with payment information, while on-site Shop forms create requests that may still need approval and payment.

Put every promise in one queue

Website checkout may create a record automatically, but cash, invoice, phone, event, and marketplace sales still create work. Add each confirmed outside order to the same operational view. Cardel Pro Admins can use Add Order for these manual sales; a custom link or external Schedule link does not create a Cardel order by itself.

Record the buyer, item, quantity, amount and currency, source, payment state, fulfillment stage, deadline, and useful instructions. Reference payment-provider IDs when relevant, but never copy card details or credentials into notes.

Set an entry rule for outside sales. The person accepting a phone order might add it before promising delivery, while an event seller might enter the day's orders before closing. A small manual step with a named owner is safer than an assumed integration.

Use four stages as a starting point

• Requested: new work needs review for payment, fit, stock, or capacity.

• Processing: the order is accepted and someone owns the next task.

• Fulfilled: the defined customer promise is complete.

• Cancelled: the work will not proceed; any payment correction is handled separately.

These are Cardel's default fulfillment stages. A workspace can rename labels, choose which appear in its pipeline, and add an Admin hint. Change a stage only when it clarifies who acts next, not to describe every minor movement.

Review new work with one checklist

1. Confirm whether the source is checkout, a request, or manual entry.

2. Verify payment without inferring it from fulfillment.

3. Check stock, schedule, location, and prerequisites.

4. Assign the next action and promised timing.

5. Move accepted work to Processing.

Decide in advance how to handle duplicate orders, unclear addresses, failed payments, unavailable items, and out-of-scope requests. Factual Admin notes should let another responsible person understand the decision later.

Communicate only useful changes

Customers need confirmation that their action arrived, notice when clarification or delay changes the plan, and a useful completion message. They do not need every internal status movement. In Cardel, a Custom Trigger email template can send a transactional message when fulfillment reaches a configured status.

Match the completion message to the offer. A parcel needs shipping or pickup detail. A digital order needs access instructions. A service may need a recap or delivered files. Generic “fulfilled” copy can close the internal task while leaving the customer unsure.

Before marking Fulfilled, keep proof appropriate to the offer: a tracking number, pickup record, delivered-file link, completed appointment, or acceptance. Then resolve contradictory payment states and send any care or support instructions.

Test and improve the loop

Run one low-value or test order from the chosen checkout, inquiry, link, or booking action through every stage. Test cancellation and a payment exception too. Review stale orders weekly and fix the smallest repeated failure first.

Useful early checks include time to first review, orders stalled in Processing, missed deadlines, cancellation reasons, and records needing correction. You do not need a broad analytics suite; a consistent weekly review can expose the bottleneck.

For on-site Shop cards, Stripe Connect handles payment through the connected account. Cardel's application fee is 0.5% on eligible sales, with a one-cent minimum on a positive charge, and Stripe processing fees are separate. Keep those fees, payment records, and fulfillment decisions distinct.

If several channels feed the queue, use the same discipline to track online and offline orders together.

To give each order a visible next step from request through completion, build your fulfillment home in Cardel.