E-commerce and retail
From paid order to shipped parcel without copying data
An online store connects the webshop, the warehouse, the courier and support, so an order moves on its own and customers can check its status themselves.
Online store with its own warehouse, 15 people
Order flow
- Order paidWebshop · card payment confirmedRunning
- Picking task createdWarehouse · three itemsRunning
- Shipping label printedCourier · tracking number assignedRunning
- Tracking sent to the customerEmail · stock updated on all channelsRunning
The build at a glance
The sector
A small online store sells through its own webshop and often a marketplace or a physical shop as well.
Every order touches the shop, the payment provider, the warehouse, a courier and the accounts. When these do not talk to each other, people carry the data between them. The same people answer customers, and most questions are about where the parcel is.
Where the time goes
Orders were exported from the webshop and typed into the courier’s tool. Stock was adjusted in the evening, so items sold out on one channel stayed on sale on another. The support inbox filled with questions about delivery, and answering each one meant opening three systems. During a promotion the team did little else but copy data and reply to the same question.
Orders are copied by hand from the shop to the courier and the warehouse
Stock differs between sales channels and overselling happens
Most support messages ask where the order is
Returns and refunds are tracked in a spreadsheet
One system around how the work is done
Support assistant
Where is my order? I paid on Monday.
Your order was handed to the courier on Tuesday and is **out for delivery today**. The tracking link is below. If it does not arrive by tomorrow, reply here and a colleague will take over.
- 01
A paid order creates the picking task, the shipping label and the invoice without anyone exporting it
- 02
One stock figure kept in step across the webshop, the marketplace and the physical shop
- 03
Tracking sent to the customer automatically, and an order status page where they can look it up themselves
- 04
A support assistant that drafts replies from order data and your policies, with a person approving anything about refunds, complaints or exceptions
- 05
Returns registered through a form that opens the task for the warehouse and the refund for approval
- 06
Webshop pages and checkout tuned for speed, so the store holds up when traffic rises
How the project runs
Four steps, one process at a time
- 01
Map the process
We follow a handful of real orders from payment to delivery, and a return, and list every manual step on the way.
- 02
Pilot one process
Order to shipping label goes live first, for one courier, alongside the old routine for a short time.
- 03
Extend
Stock sync across channels comes next, then order status self-service, returns and the support assistant.
- 04
Care
We monitor the flows, especially around promotions, and adapt them when a courier, a marketplace or the shop platform changes.
What changes for the team
- The warehouse works from a task list that fills itself
- An item sold on one channel is no longer on sale on another
- Routine status questions are answered by the status page or a drafted reply
- Refunds and exceptions are always decided by a person
An order moves from payment to the courier on its own, and stock is right on every channel. Customers find the status of their order without writing in. The team handles the cases that need judgement, such as complaints, damaged goods and refunds.
A composite scenario based on typical projects in this sector. It does not describe a named client, and the sample data is illustrative.
The same working day, before and after
What a few ordinary moments look like once the system is in daily use.
Questions from this sector
Do we have to change our webshop platform?
No. We connect what you already run, whether that is Shopify, WooCommerce or a custom shop. A move is only worth discussing if the platform itself is the obstacle.
What does the support assistant answer on its own?
Questions it can answer from your own data: order status, delivery times, return rules. Refunds, complaints and anything unusual go to a person, with the order already attached.
What happens if a connection to the courier or webshop fails?
The step is retried, and if it still fails a person is notified with the order concerned. Nothing is dropped silently.
Does invoicing change?
Invoices and fiscalisation stay in the system you already use for them. We pass the order data on so nobody has to retype it.
How do we start?
With the path from paid order to shipping label, because that is where most copying happens. Stock sync and the assistant follow.
Use cases in this story
Customers check their order without writing to you
Order and delivery status available on your site or by reply, pulled live from the shop and the courier.
Open use case Business automationERP and business systemsOrders that reach the warehouse on their own
An order placed in the shop or by email appears in the ERP, on the pick list and with the courier, entered once.
Open use case ERP and business systemsBusiness automationOne stock figure in every system
Stock levels kept in step between the warehouse, the ERP and every sales channel.
Open use caseMore sector stories
Show us one process. We will show you what it could look like.
The analysis is free, takes about an hour of your time, and ends with a written summary you keep.
Prefer to read first? See examples