Pick and pack
Wave or order-based picking, barcode confirmation at pick and pack, packing station support, and a short-pick reason code that feeds the exception queue.
Features
What the platform actually does
Every function below is part of the product that is delivered today. Where a limit or a dependency exists, it is stated next to the function rather than left to the sales call.
01 · Order intake
One queue for every channel
- Orders are retrieved at a configurable interval (default 5 minutes) and on notification, so new and changed orders arrive without manual refresh.
- Order changes and cancellations are applied to the same record, so the warehouse never picks against a stale order.
- Each order shows its channel, purchase date, promised despatch date, item count, weight and SLA age.
- Orders that cannot be matched to a mapped SKU are held in an exception queue with the reason, instead of failing silently.
- Bulk actions (hold, release, cancel, re-route) are available per order and per filter selection.
Dependency: order intake requires an active authorisation of the connected sales channel. If the authorisation expires, the queue stops updating and an alert is raised to the account administrator.
| State | Meaning |
|---|---|
| Received | Stored and validated; stock not yet allocated |
| Allocated | Stock reserved in a specific warehouse location |
| Picking | On an active pick list |
| Packed | Scanned and packed, awaiting label |
| Despatched | Label printed and tracking number transmitted |
| Exception | Held for manual decision (unmapped SKU, address issue, stock discrepancy) |
02 · Warehouse and despatch
From pick list to proof of hand-over
Carrier integration
Label generation for the carriers in your contract, including multi-parcel shipments, weight-based routing and end-of-day manifest.
Returns desk
Returns are matched to the original order, graded (sellable, repack, defect, scrap), photographed if required, and posted back to stock or written off.
Multi-site
Several warehouses can be operated in one tenant. Allocation rules decide which site serves which destination, with manual override per order.
Hand-over log
Each parcel is recorded at the moment it leaves the building: time, carrier, driver reference, parcel count. This log is the basis for carrier claims.
Roles, not shared logins
Picker, packer, warehouse lead, customer service, finance and administrator roles with separate permissions. Every action is attributed to a named user.
03 · Inventory synchronisation
One stock pool, channel-specific rules
- Available quantity is calculated from physical stock minus reserved stock, open picks and a per-SKU safety buffer.
- Each channel has its own buffer and its own maximum, so a channel promotion cannot empty the pool for everyone else.
- Synchronisation runs on change and on a scheduled sweep; conflicting updates are resolved by a defined priority order and logged.
- Inbound shipments are visible as expected stock with an arrival window, without being counted as available.
- Low-stock and out-of-stock alerts are sent by e-mail or webhook, per SKU or per channel.
What synchronisation cannot do
Stock accuracy depends on physical accuracy. If the warehouse counts are wrong, the platform will publish the wrong number faster. We therefore recommend a stocktake cadence and use the discrepancy report to find recurring causes.
04 · Amazon integration
Selling Partner API roles and data we use
Authorisation happens through Amazon's OAuth flow. The seller signs in on Amazon, chooses the account and grants access; the platform receives a refresh token and never sees the seller's password. Access can be revoked by the seller at any time from Seller Central, and revocation takes effect on the next request.
| Role (as defined by Amazon) | What we use it for | Access |
|---|---|---|
| Orders | Read orders, order items and order status; confirm despatch | Read / write |
| Inventory and Order Tracking | Read stock levels and inbound quantities | Read / write |
| Direct-to-Consumer Shipping | Transmit tracking number, carrier and despatch date back to the order | Write |
| Product Listing | Read SKU and listing attributes to map items to warehouse articles | Read |
| Reports | Retrieve settlement and inventory reports for reconciliation | Read |
| Notifications | Subscribe to order-change notifications so new orders arrive without polling delay | Read |
Role names and scopes are defined by Amazon and may change. The platform requests no advertising, taxation or pricing roles, and does not request access to buyer personally identifiable information beyond the shipping data Amazon supplies with an order.
Data fields and their purpose
| Data category | Examples of fields | Purpose | Retention |
|---|---|---|---|
| Order header | Order ID, purchase date, status, marketplace, currency, order total | Processing and reconciliation | 10 years (statutory accounting) |
| Order items | SKU, ASIN, title, quantity, item price | Pick, pack and invoice | 10 years |
| Delivery data | Recipient name, delivery address, carrier, tracking number | Despatch and returns handling | 90 days after delivery, then deleted |
| Inventory | Available, reserved and inbound quantity per SKU and location | Stock synchronisation | Current plus 24 months of history |
| Listing attributes | SKU, product title, dimensions, weight | Mapping and carrier routing | Current plus 12 months |
| Settlement reports | Fees, reimbursements, payouts | Financial reconciliation | 10 years |
05 · Reporting
Numbers your accountant and your warehouse lead can both use
Operational
Orders per hour, cut-off adherence, short picks, despatch accuracy, carrier exceptions, returns rate by SKU.
Commercial
Revenue and units by channel, fee breakdown, settlement reconciliation, stock valuation at cost.
Export
CSV export for any filtered view, scheduled e-mail delivery, and REST endpoints on the Enterprise plan.
Questions we are asked before signing
Do I need to move my stock to your warehouse?
No. The platform manages stock in your own warehouse as well as in our fulfilment centre. Using our centre is optional and priced separately.
Can I connect several Amazon marketplaces?
Yes. Each marketplace is a separate connection with its own authorisation and its own buffer rules. The Omnichannel plan includes up to five connections; further connections are an add-on.
What happens if the Amazon connection drops?
The queue stops receiving new orders and the administrator is alerted. Orders already in the warehouse continue to be processed. Once the authorisation is restored, missed orders are retrieved from the last successful checkpoint.
Is my data used for anything other than fulfilling my orders?
No. Data from connected sales channels is used solely to provide the service to you. It is not sold, published, used for advertising or shared with other customers. Details are in the Privacy Policy.
Where is the platform hosted?
In data centres within the European Union, operated by our hosting sub-processor. A list of sub-processors is published on the Security and Data page.
Want to see it with your own order volume?
We run the demo with your channel structure, not with a canned dataset.