Every order you take, however it comes in.
The ones your customer places in the store, the ones your rep enters, the ones that come in by phone. Scroll down and watch one end to end: it gets edited, the total recalculates on its own, it moves to the stage you defined and the buyer hears about it.
The list with its filters: tracking, segment, rep and payment method. #25 is NEW.
The order opens and a product gets added — a phone call, a missing item, whatever it is.
The total recalculates on its own, with that customer's list and discount. Nobody reaches for a calculator.
The stage is picked from the ones the business defined, not from a canned list.
It lands on the list and the buyer gets the notice: the email goes on its own, WhatsApp is one click.
The filters a wholesaler needs, not those of a store with three orders a day.
When dozens of large orders come in daily, the problem isn't seeing them: it's finding the six that need something today. The filters combine with each other and the search reaches into the order notes.
- A filter on every column header: date range, tracking stage, customer segment, rep, payment method and shipping method, all combinable. "Kiosk orders paid by transfer this month" is a cross-filter, not a report request.
- Search that goes deep: by number, by customer, by amount and also by whatever was written in the order notes.
- What you filtered, you export: an Excel of the list, and over the same range, a product-by-product sales report and a report by category. For bookkeeping, or to see which segment pulled.
- CSV for the ERP: the order comes out in the format your management system expects, if you need to load it outside the automatic integration.
The stages are your operation's, not a manual's.
A manufacturer doesn't dispatch like an importer, and a distributor with its own delivery fleet doesn't either. You create the stages with the names your team actually uses, and each one decides whether the buyer hears about it.
- Your own name and color: "Ready, not yet paid", "Out for delivery", "Waiting for pickup". The ones your team already says out loud.
- One notice per stage, or none: each status has its own notify switch, with its own subject and body. The email goes out on its own; the same message, already written, goes to WhatsApp with one button. Internal stages classify without notifying anything.
- You set the timing, order by order: instead of promising a fixed window from the shipping method, each stage's notice tells what is actually happening with that order.
- The list filters by stage: seeing everything stuck at one step is a click, not a walkthrough.
The order that comes in by phone is an order too.
In wholesale a good share of the selling still happens over WhatsApp, on the phone and on a rep's visit. Those orders get entered in the panel and end up identical to the store's: same list, same stages, same picking.
- Manual entry with the customer's terms: you pick the buyer and the order already carries their price list, their discount and their minimums. Nobody does the math by hand.
- Excel import: when a customer sends their restock as a spreadsheet, it comes in as an order instead of being retyped.
- Repeat a previous order: next month's restock comes out of last month's order, but at today's prices: the lines are copied into a new order and re-priced against the catalog and that customer's list. Whatever no longer exists in the catalog isn't copied.
- Notes per line: "wrap separately", "prioritize this item". The instruction travels attached to the product all the way to the warehouse.
- Two notebooks, not one: the buyer sees the observations and they go out in their emails; internal notes stay with your team, for the commercial agreement you don't spell out.
An order gets edited. What doesn't get lost is who edited it.
A wholesale order passes through the rep, the office and the warehouse, and the amounts are large. Every change is recorded with its date, its time and who made it, and the buyer gets notified when it matters.
- Who, what and when: edits to quantities and prices, stage changes, adjusted terms. All time-stamped.
- It earns its keep in a dispute: which price applied, which terms were agreed and who changed them stops being an argument from memory.
- The rep hears about it too: relevant changes notify the buyer and the assigned rep, with nobody forwarding anything.
- An order is never deleted: if it has to go, it's voided, and it still exists in the sales history. Traceability isn't sacrificed to tidy up a list.
The order reaches your management system on its own — and if it fails, you find out.
Every order syncs with the ERP you already use so stock, prices and store credit stay in sync without double entry. And every attempt leaves a record: if something drops, you see it and retry.
- Native integration with the region's ERPs: Contabilium, Dragonfish, DUX, Ninox and several more, each with its own way of connecting.
- A log per attempt and a manual retry: the order keeps what was sent, when, and with what result. A network error doesn't turn into a lost order.
- Tax details travel with the order: legal name, tax ID, tax status and address, captured at confirmation. In Argentina the tax ID autocompletes against the national registry, with no certificate to upload.
- Packing slip, label and an Excel of the order: the breakdown with quantities, prices, per-line discounts and itemized taxes prints with the buyer's tax details, sorted and grouped the way your warehouse asks for it. It works as a purchase order or sales note, and the buyer has it in their portal.
When the order reaches the warehouse, picking begins.
The picking module has its own queue, its own warehouse role and its own way of accounting for what's missing. It's the part of the circuit no ordinary ecommerce solves.
See order picking →