Wholesale purchase orders arrive as PDFs, spreadsheets, emails and portal exports — then get retyped into a warehouse system, an invoice and a spreadsheet. ThroughlineOps reads them once and carries them all the way to dispatched, invoiced and costed.
No card required to start. Your data stays in your own workspace.
The job today
The work is not complicated, it is just relentless — and every hop between a purchase order and a dispatch note is a chance to ship the wrong thing at the wrong price.
One buyer emails a PDF, another exports from a portal, a third attaches a spreadsheet with the columns in their own order. All of it gets retyped.
The code on the purchase order rarely matches the code in your warehouse, and the mapping lives in somebody's head or a spreadsheet tab.
Duty, freight and import VAT land on a shipment, not an order. Bundles have no cost of their own. Rebates are reconciled at year end, by hand.
Order intake
Upload a PDF, Excel file or CSV, or let customers email purchase orders straight to a dedicated address. ThroughlineOps extracts the header and every line, then puts it in front of you to confirm.
Scanned and photographed POs too
Text-based PDFs are read deterministically. A scan with no selectable text is transcribed by vision OCR and flagged in the review drawer so it gets a closer look.
Reusable templates per customer
Save the column layout a customer always sends and it is applied automatically next time, including their own SKU codes.
It never invents a value
If a field cannot be read it is left blank with the reason shown, and the order waits for a human. A failed extraction is never dressed up as a real order.
Checks before anything ships
Duplicate purchase orders, unmapped SKUs and prices that differ from the agreed list are all surfaced before you confirm.
Fulfilment
Once an order is confirmed, its SKUs are translated to the codes your warehouse actually uses and sent on — by API, by webhook, or as a CSV export for a 3PL that works that way.
SKU translation built in
Map a customer's code to your internal product once. Every future order from them resolves automatically, including pack sizes and multipliers.
Any warehouse or 3PL
A documented, provider-neutral integration means a partner can accept orders and post dispatch confirmations back without custom work on your side.
Tracking flows back
Dispatch numbers, carrier and tracking references return automatically and update the order, so nobody chases the warehouse for a status.
Nothing ships half-mapped
An order with an unrecognised SKU stops in Needs attention rather than going out wrong.
Reporting
Sales, cost of goods and gross margin by customer, by product and by reporting group — calculated from the orders themselves rather than reassembled in a spreadsheet each month.
Bundles cost what their components cost
A gift set with no cost of its own is priced from its bill of materials, nested several levels deep if that is how it is built.
Unknown is never treated as free
A product with no known cost is excluded from margin and counted in a missing-cost total, so a gap shows up instead of flattering the number.
Customer rebates accrued as you go
Retro schemes are tracked against each customer's agreed tiers all year, with the rate applied to the whole qualifying intake — not just the amount above the threshold.
Everything exports
Every report downloads as CSV with the same figures on screen, for the finance pack or the accountant.
Purchasing and logistics
Customs duty, import VAT and freight are charged against a shipment, but a shipment usually carries goods for several purchase orders. ThroughlineOps apportions them so each order carries its share.
The basis is always stated
Customs value where every line has one, then weight, then quantity. The basis used is shown next to the figure, so it can be explained rather than merely trusted.
Pennies reconcile exactly
Allocated amounts always sum to the charge on the shipment — no rounding drift to explain to an auditor.
Customs entry kept with the order
Entry number, clearance status, origin and arrival date stay attached to the purchase order for audit.
Supplier POs through to goods-in
Raise supplier orders, receive against them, and have stock and incoming quantities update as they arrive.
The rest of it
Everything a wholesale operation touches between a purchase order and a finance pack, in one place with one set of numbers.
A dedicated address per workspace. Customers email a PO and it appears ready for review, attachments and all.
Stock levels across warehouses, with low-stock thresholds and reorder points.
Production orders and scheduled call-offs, received into stock the same way as supplier orders.
Projected cover from real demand, with reorder recommendations that turn into supplier POs.
Raise invoices from completed orders and push them to your accounting system.
Shipments from booking to arrival, with ports, carrier, incoterms and clearance status.
Export documentation generated from the order, with HS codes, origin and customs values.
Import retailer and marketplace sales reports to see what is actually selling through, by store and by week.
Packaging weights by material and component, multiplied by units sold, for extended producer responsibility returns.
Month-to-date actuals against forecast, with run-rate projections during your busiest trading periods.
Owner, admin and staff roles scoped per workspace, with an audit log of who changed what.
A standing scan for weak integration settings, stale connections and unused access.
Channels and integrations
Marketplace, ecommerce and wholesale orders land in the same queue, translate to the same SKUs and report against the same costs.
Connect your Selling Partner account over SP-API — authorisation and encrypted credential storage are in place, and the connection can be tested against live order data. Automatic order importing is still in build. Today, Amazon shipment and inventory reports load through the report importer, so Amazon demand sits alongside every other channel in forecasting, margin and sell-through reporting.
SP-API connection · Report import · Order sync in build
Connect a store and orders arrive automatically, with fulfilment and tracking pushed back once the warehouse dispatches.
Orders · Fulfilment · Cancellations
Raise invoices against completed orders and send them to Xero, with the invoice number and status kept on the order.
Invoices · Contacts · Item codes
A provider-neutral API any warehouse can implement, plus CSV export and inbound webhooks for partners who prefer files.
Orders out · Dispatch and stock back
Security
Purchase orders, price lists and margin are among the most sensitive things a brand has. The controls below are structural, not settings someone has to remember to switch on.
Every record carries a workspace and is enforced at the database with row-level security, so one customer's data is not reachable from another's session.
All traffic is served over TLS. Data is stored in managed Postgres with encryption at rest, hosted in the UK/EU region.
API keys and OAuth tokens for connected platforms are encrypted with a separate key and are never returned to the browser.
Inbound webhooks are verified by signature or shared secret before anything is written, and an unverifiable request is refused rather than trusted.
Owner, admin and staff roles gate every action server-side. Permissions are checked on the server, not just hidden in the interface.
Changes to orders, connections, pricing and team access are written to an append-only audit log with the acting user and timestamp.
Data use
ThroughlineOps is used by a brand to run its own operations. Where a customer connects a marketplace, ecommerce or accounting account, we access only what is needed to do the work they have asked for, on their instruction, as their processor.
Security, privacy and data-protection enquiries: privacy@throughlineop.co.uk · Product and account support: support@throughlineop.co.uk
Pricing
Every feature on this page is included. Pricing is per workspace, not per order, so automating more of your business never costs you more to run it.
The full product — intake, dispatch, purchasing, logistics, reporting and every integration. Monthly or annual billing.
Multiple brands or warehouses, bespoke customer templates, or a specific EDI or portal requirement — talk to us and we will scope it.
Talk to usQuestions
No. That is rather the point — they keep emailing whatever they already send, and ThroughlineOps reads it. If a customer always uses the same layout, you can save it as a template so future orders map straight through.
The upload is kept with every field blank and the reason shown, and it waits for someone to key it in. Nothing is ever guessed or filled with placeholder data, because an invented order can be confirmed and shipped.
If your warehouse or 3PL can accept an HTTP request or a CSV file, yes. The integration is documented and provider-neutral, and dispatch confirmations come back by webhook.
Yes. Invoices are raised from completed orders and pushed across, with the invoice number and status kept against the order so you can see what has been billed.
A workspace is usable the day you sign up. The work is loading your product catalogue and mapping customer SKUs — for most brands that is days, not months, and you can start with one customer.
You do. It is your workspace, it exports at any time, and disconnecting a platform revokes the stored token immediately.
Start with one customer and one warehouse. If it does not save the person doing this job an afternoon a week, it is not worth paying for.