The Orders Your Cin7 Portal Never Catches
Your Cin7 B2B portal and EDI links handle the customers who order the way Cin7 expects. Everyone else emails a purchase order. We read those orders and create them in Cin7 Core or Omni through the API, priced and allocated correctly, so the middle of your order book stops being typed in by hand.
Core Or Omni
Built for the way you run Cin7, whether that is Cin7 Core or Cin7 Omni, creating sales orders through the API into your existing setup.
Past The Portal And EDI
Automates the orders the B2B portal and EDI never cover: the PDFs, spreadsheets and emails your customers send instead.
Cin7 Pricing Applied
We apply the price tier or customer pricing Cin7 holds for each account and validate every line against it before the order posts.
Right Branch, Right Stock
Orders are created against the correct customer and branch or location, so allocation and stock stay accurate.
Exceptions Held
Duplicate references, price mismatches, missing details and unmatched products are parked for review rather than pushed through.
Bespoke And UK-Built
A developer-led build against the live Cin7 API, shaped around your accounts and pricing, delivered under NDA.
Some of our direct clients
Portal, EDI, And Then Everyone Else
Cin7's portal and EDI serve the customers who fit them. This automates the large share who email their orders instead.
- 5+
- Order formats read (PDF, CSV, Excel, Word, email)
- 0
- Off-portal orders keyed into Cin7 by hand
- 100%
- Orders retained with a full audit trail
- 2 days
- Typical quote turnaround

Cin7 Developers For The Off-Portal Orders
We build against the Cin7 API so the orders that never fit your portal or EDI are read, priced and created automatically in Core or Omni.
- Sales orders created via the Cin7 API
- Cin7 price tier validation
- Correct branch and location allocation
- Exception review queue
Off-Portal Orders Into Cin7
We map your Cin7 setup
We look at how your account is priced and structured, which customers order off-portal, and how those orders reach Cin7 today. A few real purchase orders tell us most of what we need.
We scope and quote
Using your samples, product list and pricing, we define what gets read, validated and created in Cin7. You get a fixed-price proposal with scope and timeline.
We build on the Cin7 API
We build the reading, pricing validation and sales-order creation against the live Cin7 API, testing on your real orders with everything held in review first.
We go live and raise the automation
We launch with review on every order, then switch on automatic creation for orders that meet your confidence rules, so off-portal orders flow into Cin7 on their own.
Half your orders still bypass the portal?
Send us a few of the purchase orders your customers email instead of using the portal, and we will show you how they can be created in Cin7 automatically, with a fixed quote usually within 2 working days. NDA first, no obligation.
Here's What Our Partners Say
Agencies, direct clients and long-term retainers. Rated 5* on Google.
Frequently Asked Questions
Automating Off-Portal Orders Into Cin7
Cin7 gives you a portal, EDI and native channel links, and they work well for the customers who fit them. The orders that cause manual work are the ones that fit none of those: the buyer who emails a PDF instead. Here is how we automate that middle of the order book into Cin7.
The order book Cin7's own tools miss
Cin7 is designed around three tidy ways an order can arrive: through the B2B portal, over EDI, or from a connected sales channel. Each is efficient, and each only covers a specific kind of customer. The portal needs the customer to log in and order themselves. EDI needs an account large and structured enough to warrant it. Channels only carry channel orders.
That leaves a substantial group who simply email a purchase order, and every one of those lands on a person to interpret and key into Cin7. This is the exact gap we automate, so the off-portal order book stops being manual.
Reading orders and applying Cin7 pricing
We read PDF, CSV, Excel, Word and email-body orders, trained on the formats your customers use, and pull out the customer, purchase order reference, delivery address and each product line. Customer codes are mapped to your Cin7 products, with unmatched lines flagged rather than guessed.
Pricing is where wholesale gets it wrong most, so we apply the price tier or customer pricing Cin7 already holds for the account and validate each line against it. That means an order is priced on the agreed terms, not on whatever the buyer's document happened to show.
Not sure your off-portal orders can be automated?
Send us your most awkward emailed orders. We will tell you honestly what can be created in Cin7 automatically and what needs a review step.
Created in Core or Omni, allocated correctly
Validated orders are created in Cin7 Core or Omni through the API as sales orders, against the correct customer and branch or location, so stock allocation and downstream invoicing stay accurate. Duplicate purchase order references are caught before they cause a second despatch.
If some of these orders currently detour through Shopify to reach Cin7, creating them directly removes that step and its fee. This is a focused part of our broader automated order processing service, and pairs with wider API integrations when Cin7 needs joining to the rest of your stack.
A careful, bespoke rollout
Orders are reviewed first while we tune the reading on your real formats and confirm pricing behaves exactly as it should, and only orders that clear your confidence rules then post automatically. Every original document is kept and every extracted field logged.
It is a developer-led build shaped around your Cin7 setup, delivered by a UK team against the live Cin7 API under NDA. If you also run Linnworks or Unleashed, the same approach is available through our Linnworks order automation and Unleashed order automation.
Partner with Zestcode for Industry Leading Quality and Reliability
Tell what you're looking for and we'll see you how we can help. Quotes are typically provided within 2 working days of the initial call.