Skip to content
QuickE
Start free

Order management

Every order, one queue

Orders come in from your store, from a spreadsheet upload, or through the API, and land in the same queue with the same fields. Your team filters it, searches it and acts on the whole selection at once, instead of retyping orders between systems.

Start freeBook a demo

Three ways in, one queue

A connected store pushes orders as customers place them, a spreadsheet upload takes the file a merchant already sends, and the API accepts orders from any system that can post them. Whatever the door, the order arrives with the same fields in the same queue, so the person dispatching never checks three places to know what today looks like.

Spreadsheet upload with a saved mapping

Match the file’s columns to order fields once and the mapping is saved for that layout, so the same merchant’s file imports next week with no setup. Rows that fail validation are listed with the reason on each, the clean rows import anyway, and a corrected row can be uploaded again without creating a duplicate.

Filters, search and saved views

Filter by status, merchant, zone, payment type, assigned driver or date, and search by order reference, customer name or phone number, because the phone number is what a caller actually gives you. A filter you run every morning can be saved as a view, so unassigned COD orders for today is one click rather than a routine.

Bulk actions with a record

Select the filtered set and act once: assign to a driver, hand to a carrier, move between hubs, print waybills, change status or export. Each bulk action is logged with who ran it, when and on which orders, so a wrong assignment is traced in minutes rather than argued about.

What you stop doing

  • The order list pasted into a WhatsApp group every morning.
  • The master spreadsheet only one person is allowed to touch.
  • Retyping an order from the store screen into the delivery sheet.

Where this matters most

See e-commerce and retailSee 3PL and courier companies

Questions operators ask

How do orders get into the queue?
Three ways: a connected store pushes orders as customers place them, a spreadsheet upload imports the file a merchant already sends, and the API accepts orders from any system that can post them. All three arrive in the same queue with the same fields, so the source of an order never changes how it is worked.
Do I have to map the spreadsheet columns on every upload?
No. The mapping between the file’s columns and the order fields is saved the first time, so a file with the same layout imports with no setup. A merchant who sends a differently shaped file gets their own saved mapping.
What happens to rows that fail in an upload?
The failed rows are listed with the reason on each one, such as a missing phone number or an area the system does not recognise, and the clean rows import anyway. Fix the listed rows and upload them again, and the orders already imported are not created a second time.
What stops the same order being created twice?
Every order carries a reference from its source, a store order number, a row in a file or an API id. An incoming order whose reference already exists in the queue is flagged as a duplicate instead of being created again, so a re-sent file or a retried API call does not double the day’s work.
Can I act on many orders at once?
Yes. Filter the queue down to the set you mean, select it and apply one action: assign to a driver, hand to a carrier, move to another hub, print waybills, change status or export. The action is recorded with who ran it, when and on which orders.

Get tomorrow’s orders into one queue

Start free, upload tomorrow morning’s file and dispatch it from one screen. Or book a demo and walk through how orders reach you today with someone who has watched it done in a WhatsApp group.

Start freeBook a demo