Integration
Cin7 handles inventory, allocation and pick pack ship. Shopify holds the catalogue and the B2B accounts. LevelOps PDF to Order fills the gap in front of both, turning emailed purchase orders into validated Shopify draft orders before your Cin7 connector picks them up.
Cin7 is inventory and order management rather than a classic ERP, and that is exactly why merchants pick it. Cin7 Core, formerly DEAR Systems, holds products and stock across locations, runs assembly and simple production, drives pick pack ship, syncs to Xero or QuickBooks, and offers a B2B portal. Cin7 Omni adds heavier channel management, 3PL and EDI. Both ship a native Shopify integration.
The usual architecture is clean. Cin7 owns products, stock and price tiers, and pushes them into Shopify. Shopify owns the storefront, the company accounts and the checkout. Orders created in Shopify flow back to Cin7 as sales, and Cin7 takes over allocation, picking and invoicing.
What that architecture does not include is the wholesale buyer who emails a purchase order. Their procurement system spits out a PDF, or somebody exports a spreadsheet, and it lands in a shared inbox. Neither Cin7 nor Shopify reads it. A member of your team does, then types it into Shopify or into Cin7 by hand. LevelOps PDF to Order removes that step and leaves the rest of your stack untouched.
Cin7 shops tend to be lean, multi channel and growing fast. That combination makes manual intake expensive in a very particular way.
Cin7 merchants rarely have a large back office. When inbound POs spike, there is no bench. Orders queue in an inbox, and your best accounts feel it first because they order the most.
Some reps key a PO into Shopify so the connector handles it. Others key it straight into Cin7 to skip the sync wait. You end up with sales in Cin7 that have no Shopify order behind them and reporting that never quite reconciles.
The portal works, and the buyers who adopted it are no longer a problem. The remaining accounts either refuse to log into a supplier portal or are contractually bound to their own procurement system.
Cin7 price tiers and Shopify B2B price lists both exist. When they drift, the price a rep types from the PDF is not the price either system holds, and the difference is found at invoicing.
Cin7 is only as accurate as what is entered against it. An order typed with the wrong variant allocates the wrong stock, triggers the wrong reorder, and quietly corrupts the numbers you make purchasing decisions on.
Every new distributor, retailer and marketplace brings a new document layout. A parser you configure per sender becomes another thing to maintain, which is why template based tools fail in a Cin7 style multi channel business.
The order reaches Cin7 exactly as it does today, through Shopify. It simply arrives correct instead of arriving as an attachment.
Forward it to your dedicated LevelOps address, or upload it from the Shopify admin. No portal to sell to your buyer, no template to maintain.
Products, quantities, units, requested dates and the PO number come off the document, and every line is matched against the Shopify catalogue Cin7 publishes.
Your rep sees the draft order with the source file attached, checks the flagged lines and approves. Nothing is committed and no stock moves before that.
Approved drafts become normal Shopify orders, so the native Cin7 Shopify integration creates the sale on your existing mapping. Allocation, picking and invoicing continue in Cin7.
LevelOps writes to Shopify natively. Cin7 receives these orders through the same connection it already uses, which is why there is nothing to configure on the Cin7 side.
A field level view of the division of labour between the document, Shopify and Cin7.
Extraction happens before anything is created, so a bad document never becomes a bad order.
A normal draft order, built from your Shopify data rather than from the PDF.
Whatever your Cin7 Shopify connection already maps. These orders are not a special case.
The things LevelOps deliberately does not do.
In a Cin7 shop the product master lives in Cin7 and Shopify is the published face of it. PDF to Order matches against the Shopify catalogue precisely so that every matched line points at something that can be priced, sold and synced back without a manual fix.
That makes catalogue coverage the one thing worth checking before you start. If your buyers order items that exist in Cin7 but were never pushed to Shopify, those lines get flagged for a person instead of matched. It is the safe behaviour, and in practice it surfaces the products your team has been meaning to publish for months. Fixing that list is usually a short piece of data work, and it improves your storefront at the same time.
Pricing follows the same principle. The price on a purchase order is a claim, not a fact, and buyers frequently print an old one. PDF to Order applies the price your Shopify company account holds, so the draft reflects what you actually agreed. That only works when Cin7 price tiers and Shopify B2B price lists agree, so we check that alignment during the audit and tell you plainly where they have drifted. Customer specific part numbers need no maintenance in either system, because matching handles the buyer's own codes and loose descriptions directly, and gets better as your team corrects it.
If you already run the Cin7 B2B portal, this is the group that keeps landing in your inbox. PDF to Order is aimed squarely at them.
You can start with the app on its own. Where the Cin7 side needs attention, our implementation team works on Cin7 directly.
We take a real sample of the POs your team handled last month, group them by account and format, and estimate how much of that volume the app covers today. No promises based on someone else's numbers.
We compare the Cin7 product master against the Shopify catalogue, and the Cin7 price tiers against your Shopify B2B price lists. Gaps get listed in priority order, with the cheap fixes first.
Start where the pain is. Your team reviews every draft order, corrections train the matching, and you measure against your own baseline for a couple of weeks before widening scope.
If the Cin7 to Shopify sync, warehouse setup or product data is the real bottleneck, that is an implementation engagement rather than an app problem. Our ERP and MRP implementation page explains how those run.
Cin7 is one of the five platforms our implementation team delivers on, with fixed fee scope and defined milestones. Detail at /en/erp-implementation.
Four ways to get an emailed purchase order into Cin7. Only one of them requires nothing from the buyer.
| Manual entry | Cin7 B2B portal | EDI on Omni | LevelOps PDF to Order | |
|---|---|---|---|---|
| Reads a PDF or spreadsheet PO | A person does | No | No | Yes |
| Buyer has to change how they order | No | Yes, they must log in | Yes, full onboarding | No |
| Matches the buyer's own part numbers | From memory | Not applicable | Mapped per partner | Yes |
| Human approval before the sale exists | Yes | Order is placed directly | Usually automatic | Yes |
| Cost to add one more account | More headcount | Onboarding effort | New partner setup | None |
| Handles a new document layout | A person adapts | Not applicable | New mapping project | No template needed |
| Time to first live order | Immediate, forever | Weeks of adoption | Months per partner | Days |
| Where the order is created | Shopify or Cin7 by hand | Shopify or Cin7 portal | Straight into Cin7 | Shopify draft, then your connection |
Rated 5.0 on the Shopify App Store, with wholesalers and distributors running the same Shopify first flow.
It is literally reading my PDF and uploading a 100+ item order in under 4 minutes. This just made us 10x more efficient.
Manually processing B2B orders is something you simply have to deal with if you want to keep specific customers. LevelOps reads orders in various formats and converts them to draft orders for final review.
Because orders processed through LevelOps require a quarter of the time that full manual orders require, our team has gained considerable time back, which is now dedicated to more complex, valuable tasks.
Amazing team and product. Will save countless hours manually entering emailed B2B orders. Highly recommend to anybody selling wholesale.
No. PDF to Order writes a validated draft order into Shopify. Once a person approves it, the Shopify order flows to Cin7 through the native Cin7 Shopify connection you already run, which creates the sale in Cin7 with your usual mapping. There is no separate Cin7 integration to install, and no second path into your inventory.
Yes, because the app never touches Cin7. Core, formerly DEAR Systems, and Omni both pull Shopify orders through their own Shopify integration, so both receive these orders the same way they receive every other Shopify order. The difference between the two shows up in what happens after the sale is created, not in intake.
Because portals cover the accounts willing to use them. The accounts that will not are usually your largest ones, the buyers whose own procurement system generates a PDF and emails it. PDF to Order covers exactly that group without asking them to change anything, so the portal and the app together get you closer to full coverage than either alone.
Cin7 pushes products and stock to Shopify, and PDF to Order matches against that Shopify catalogue. Lines resolve on SKU, on barcode, and on loose description including the buyer's own part numbers. Anything sitting in Cin7 but not published to Shopify is flagged for a person, which usually exposes a catalogue coverage gap worth fixing anyway.
Whichever system holds the price your customer was promised should own it. If your Cin7 price tiers are mirrored into Shopify B2B catalogues and company price lists, PDF to Order applies the correct account price automatically and ignores the price printed on the PDF. If the tiers are not mirrored, we flag the mismatch during the audit, because a price applied at intake and corrected in Cin7 later is a dispute waiting to happen.
No, and that is deliberate. A draft is not an order, so nothing is committed until a person approves it and the Shopify order is created. Allocation, backorder handling and partial fulfilment continue to be decided in Cin7 exactly as they are today.
Keep them on EDI. EDI is the right channel for a high volume partner who supports it. PDF to Order is for the long tail that EDI never economically covers, plus the partners whose EDI documents still arrive as attachments. The two are complementary, not competing.
Both are extracted from the document and written onto the Shopify order, where your Cin7 connection can carry them into the sale reference and required date fields. The source file stays attached to the draft, so anyone who questions a line later can open the original.
Yes. Cin7 is one of the platforms our implementation team works on, alongside Katana MRP, MRPeasy, Odoo and Business Central. If the real problem is that your Cin7 to Shopify sync, product data or price tiers are not clean, we would rather fix that than sell you an app that trips over it.
Install from the Shopify App Store and your catalogue syncs in a few minutes. Most teams process live purchase orders in their first week, with your first 5 orders free, with no expiry to validate the extraction on real documents before any commitment.
Cin7 is one of the five platforms our implementation team delivers on.
Read, match, price, approve, step by step.
Why a portal and an intake app solve different halves of the problem.
The operating model around inventory, accounts and terms.
The wider case for automating the intake side first.
The same pattern for merchants running a lightweight manufacturing ERP.
Send us three real purchase orders from the accounts that refuse your portal. We run them live and show you the draft orders, matched lines and flagged exceptions on your own catalogue.
your first 5 orders free, free allowance of 5 orders, bilingual support in English and French.
