Move orders through your workflow, not ours
Marketplace statuses describe what the channel thinks. Custom statuses describe what your business is actually doing — awaiting supplier, in production, ready for courier, on hold for fraud check — and flows move orders between them automatically.
- Your own status names, grouped into stages
- Runs alongside the native order status, never replaces it
- Flows apply and change statuses automatically
HOW IT WORKS
Describe your process, then automate it
Custom statuses are a layer you own, parallel to the channel status.
Name your statuses
Create the labels your team actually uses in conversation. If your warehouse says "waiting on the supplier", that becomes a status rather than a note nobody reads.
Group them into stages
Statuses belong to groups, so the order list can show a tidy set of stages in the sidebar instead of a flat list of thirty labels.
Let flows do the moving
A flow action changes an order's custom status, so orders advance when the underlying event happens rather than when somebody notices.
Notes in a spreadsheet vs statuses in the system
Doing it by hand
- Track "waiting on supplier" in a side spreadsheet
- Free-text notes nobody filters on
- Marketplace status says Processing for four days
- New staff learn the workflow by asking
- Nobody knows how many orders are stuck where
With easySales
- Every stage of your process is a filterable status
- The order list is the single source of truth
- Your stage and the channel stage both visible
- The workflow is self-documenting
- Counts per stage, live in the sidebar
YOUR WORKFLOW
A status layer that fits how you actually operate
Parallel to the marketplace status, not instead of it
The channel still needs its own status, and easySales keeps syncing it. Your custom status sits alongside, which means you can be honest with the marketplace and precise internally at the same time.
Statuses that assign themselves
A flow action sets the custom status, so orders route themselves: a failed VAT check moves the order to review, a stockout moves it to awaiting supplier, a completed pack moves it to ready for courier. Your board reflects reality without anyone dragging cards.
A starting status for every new order
Orders can be given an initial custom status the moment they arrive, so nothing sits in an undefined state. That is a separate mechanism from the flow engine, which means your entry point is guaranteed even before any rule runs.
Restrict statuses per team member
Not every status should be available to everyone. Access can be limited per team member, so a packing operator sees the stages they work and cannot move an order into a finance-only state by accident.
"Our board matches reality"
"No side spreadsheets"
"New staff onboard faster"
What routing connects to
Ready to put your real workflow in the system?
Name your stages, group them, and let flows move orders between them.
Start free trialFrequently Asked Questions
Have a question? Contact us and we'll be happy to help.