When Stripe accepts a payment, Setka creates a paid order, updates inventory, sends the customer a confirmation, and notifies the merchant. The paid order in Setka is the source for fulfilment; you do not need to open Stripe and reconcile every successful payment before touching the parcel.
Your work starts with the promise recorded on that order. Confirm what the customer bought, where it must go, and how it should be delivered. Then handle the physical goods carefully and keep the order status and customer communication aligned with real events.
The paid-order workflow
Successful payment
|
v
Paid Setka order + inventory update + notifications
|
v
Check customer, delivery, products, quantities, and totals
|
+---- unclear detail or physical problem ----> PAUSE + resolve
|
v
Pick -> inspect -> pack
|
v
Prepare shipment -> add tracking -> update status
|
v
Send the message supported by the real event
This is deliberately a short chain. Setka has already connected checkout, payment, inventory, and the order. The merchant adds the physical and customer-service judgment that software cannot provide: Is this the right item? Is it undamaged? Is the address complete? Is the parcel ready for the selected service?
1. Open the paid order and read it once from top to bottom
Work from the order in Setka, not from an email notification or a copied message. Check:
- customer name and contact details;
- delivery address or pickup point;
- selected shipping method;
- product names, identifiers, options, and quantities;
- prices, discounts, shipping charge, tax, and final total; and
- any customer note that changes packing or delivery.
Do not silently correct a meaningful address detail. If an apartment number, postcode, pickup point, or destination conflicts with the rest of the order, pause and ask the customer for the missing fact through a trusted contact channel.
The paid status in Setka is authoritative. Open Stripe only when you are investigating a genuine exception such as an unexpected status, dispute, refund issue, or support case.
2. Confirm the physical goods
Setka updates inventory after successful payment. The next check is physical: make sure the recorded item exists, is the correct option, and is fit to send.
Match each line by SKU or another stable identifier rather than packaging color alone. Check the exact quantity and inspect the product and retail packaging for damage. If something is missing or damaged, keep it out of the parcel and follow the exception path below instead of substituting a similar item without the customer’s agreement.
Good catalog records make this faster. The product and category preparation guide shows how clear names and identifiers reduce picking mistakes.
3. Pick and pack from one order
Keep one open order at each packing position. For every line:
- Read the identifier and quantity from Setka.
- Find and inspect the physical item.
- Place the exact quantity in the order’s packing area.
- Mark the line complete only after the item is physically present.
- Compare the finished selection with the order before sealing the parcel.
Choose packaging for the product’s weight, fragility, temperature, leakage risk, and journey. Include only the documents and inserts approved for the business. If the carrier service depends on parcel dimensions, weigh and measure the sealed parcel rather than relying on the product dimensions alone.
4. Prepare shipping and update the order
Use the delivery method recorded on the order. Before buying or printing a label, compare the recipient, destination or pickup point, parcel count, and selected service with the order.
When tracking is available, add the tracking number in Setka. Update the order status as the parcel moves through the process. A created label is not always a dispatched parcel, so use status names and customer messages that match the event that actually occurred.
For storefront rates and eligible destinations, use the shipping zones and delivery rates guide. Carrier booking and physical handoff still follow the service chosen by the merchant.
5. Communicate facts, not optimistic guesses
Useful messages correspond to real events:
- Order confirmed: identifies the order and gives the customer a way to report an error.
- Clarification needed: asks for one missing address or order detail without requesting payment credentials.
- Parcel prepared: says preparation is complete but does not imply carrier acceptance.
- Parcel dispatched: includes the valid tracking reference when available.
- Delay or stock problem: explains what changed, the available choices, and when the next update will arrive.
“We will update you by 15:00 tomorrow” is more useful than “as soon as possible” when you can genuinely meet the deadline.
Handle exceptions from the order
| Exception | Immediate action | Next decision |
|---|---|---|
| Order is not marked paid | Do not fulfil it as a paid order | Investigate the exceptional status in Setka and Stripe or contact support |
| Address or pickup point is incomplete | Pause label purchase and contact the customer | Continue after the missing detail is confirmed |
| Product is missing or damaged | Isolate the issue and stop that line | Offer the choices allowed by the store policy; do not invent a substitute |
| Customer requests a change or cancellation | Pause work if the parcel has not left | Decide from the order stage and published policy |
| Full or partial refund is appropriate | Record the decision and customer communication | Issue the full or partial refund from the Setka order |
| Parcel is damaged before handoff | Do not dispatch it | Repack or replace the affected goods before continuing |
Setka lets the merchant manage orders, update status, add an optional tracking number, and issue full or partial refunds. The merchant decides the returns, cancellation, replacement, and communication policy.
Printable first-paid-order runbook
- Open the paid order in Setka.
- Check customer contact, delivery address or pickup point, and shipping method.
- Check every product identifier, option, quantity, price, and discount.
- Confirm that the physical goods exist and are undamaged.
- Pick one order at a time from the Setka record.
- Recheck every item before sealing the parcel.
- Use packaging suitable for the product and delivery journey.
- Compare the shipping label with the order.
- Hand the parcel to the selected service.
- Add tracking when available and update the order status.
- Send only the message supported by the current event.
- Record and own any exception instead of leaving it implicit.
- Review what was unclear before the next order arrives.
Use this runbook on the first paid order and improve it from the friction you actually observe. The goal is not paperwork. It is a repeatable path from an authoritative Setka order to the correct parcel and an informed customer.