Tradelink orders, with invoice return
Tradelink purchase orders raised as Cin7 sales, and invoices sent back.
Live
Built for Cin7 Core
EDI and integrations, built for Cin7 Core.
Cin7Flow collects orders from your retailers and trading partners, checks them and raises the sales in Cin7. Invoices and files go back the other way, on the partner's schedule. Nobody re-keys a thing.
Already a client? Log in to Cin7Flow
- Purchase orders in
- Invoices back out
- SFTP and FTP
- Stock transfers
- Alerts that say what to fix
FlowRetail orders → Cin7 Core
Running
- Collected
- Checked
- Mapped
- In Cin7
- Returned
| File | Lines | Result |
|---|---|---|
| PO-4471823.json | 14 | SO-10482 created |
| PO-4471824.json | 3 | SO-10483 created |
| PO-4471825.json | 8 | Held: unknown SKU |
| PO-4471790.json | 6 | Resent, no changes |
✓41 orders into Cin7 today, 1 waiting for you
Australian owned and supportedMade in Brisbane
Built by Cin7 Core consultants25+ years of ERP projects
Hosted in SydneyWith a fixed IP for partner firewalls
Live orders every dayFor Australian suppliers
The problem
Partner orders shouldn't arrive by email and leave by keyboard.
Every retailer and trading partner has their own files, codes and rules. Cin7Flow handles all of it between their server and your Cin7 Core.
Without Cin7Flow
Someone keys every order, line by line.
- Monday morning starts with a pile of partner orders to re-key into Cin7.
- A mistyped SKU or price only shows up when the invoice is rejected.
- Invoices and tracking go back to each partner in a different format, by hand.
- A resent order quietly becomes a second sale.
- Nobody notices the feed has stopped until a customer rings.
With Cin7Flow
Orders arrive in Cin7 on their own.
- Orders are collected from the partner's folder and raised as Cin7 sales, on the schedule you choose.
- Partner codes are translated to your SKUs, customers and locations through one list.
- Invoices go back in the partner's format, once invoiced or once despatched.
- A resent order is compared with the sale in Cin7 before anything is created.
- A problem holds the order and emails the person who can fix it.
How it works
From your partner's file to a Cin7 sale in four steps.
Cin7 Core stays your system of record. Cin7Flow does the collecting, checking, translating and sending back.
We scope the flow
One call to agree the partner's files, your Cin7 settings, and what goes back to them.
We build and test it
We map the partner's fields and run their real files through our staging server.
You run it in parallel
Orders arrive in Cin7 as drafts while your team checks them against what they keyed.
It runs on its own
Switch to authorised and stop keying. Cin7Flow emails you when an order needs a decision.
Inside Cin7Flow
Built for the moment something doesn't fit.
Clean orders are the easy part. What makes an integration trustworthy is what it does with the awkward ones.
Problems wait for a decision, not a developer.
An order with a problem is held with a plain-English reason, and the person who can fix it gets an email. Fix the cause, press Try again, and it goes through.
- Unknown SKUs, price differences and credit limits caught before Cin7
- Resent orders compared with the sale already in Cin7
- Void the original and import, import as a second sale, or ignore
- Edit an order in a simple form. No JSON, no developer
Waiting for youPO-4471790 was sent again, with changes
The partner changed 2 lines after SO-10471 was created in Cin7.
| Line | In Cin7 | New file |
|---|---|---|
| PL-2200 Mixer tap | 4 | 6 |
| PL-3105 Flexi hose | 2 | 0 |
| PL-1190 Washer pack | 1 | 1 |
Their codes, your codes, one list.
Retailers send their own product numbers, store codes and tax codes. Cin7Flow translates them through cross-references your team can update themselves.
- SKUs, customers, locations and tax rules
- One list per flow, checked every time an order arrives
- A new store or product is a new row, not a support ticket
Cross-referencesRetail partner → Cin7 Core
| Type | Partner sends | Cin7 uses |
|---|---|---|
| SKU | 9310441 | PL-2200 Mixer tap |
| SKU | 9310442 | PL-3105 Flexi hose |
| Customer | Store 0231 | Sample Plumbing Co, Penrith |
| Location | DC-NSW | Sydney warehouse |
| Tax | GST10 | GST on Income |
Kept up to date by your team
It goes both ways.
In most integrations, sending documents back to the partner is half the work. Cin7Flow writes invoices in the partner's own format and drops them where they expect them.
- JSON, CSV or pipe-delimited files
- Sent once invoiced, or held until despatch so tracking is included
- A cancellation sent when a sent invoice is voided
- The Cin7 sale marked, so your team can see what went
Sent to the partner's folder at 6:02 amINV-77369.txt
HDR|INV-77369|PO-4471790|20261014|SO-10471
LIN|1|9310441|6|42.50|255.00
LIN|2|9310443|1|18.90|18.90
FRT|35.00
END|2|308.90|30.89|339.79✓ Sale marked in Cin7: sent to partner
Silence means it's working.
No inbox full of green ticks. Cin7Flow emails when something needs a person, sends one summary a day, and tells us straight away when the fault is ours to fix.
- Alerts to the right person for each flow
- A daily summary of what was handled for you
- Server and Cin7 connection faults come to us, not you
- A full history of every file: collected, checked, delivered, archived
Cin7Flowto orders@yourcompany.com.au
7:00 am
Daily summary: 38 orders in, 1 needs you
- 38 orders raised in Cin7
- 36 invoices sent back to partners
- 2 resent orders matched Cin7 and were filed
- 1 order held: customer over credit limit
Integrations
What Cin7Flow connects today.
Each connection is a flow: where the data comes from, what happens to it, and where it lands in Cin7 Core.
Mitre 10 orders
Mitre 10 purchase orders raised as Cin7 sales.
LivePartner order feeds over SFTP or FTP
JSON or CSV order files from any partner's folder, raised as Cin7 sales.
LiveInvoice files back to partners
Invoiced Cin7 sales written to a partner's folder in their format.
LiveStock transfers from a spreadsheet
One Cin7 stock transfer per row, from an upload or a folder.
LiveMove files between servers
Copies files from one SFTP or FTP folder to another, on a schedule.
LiveBuilt by people who implement Cin7 Core for a living.
Cin7Flow is made in Brisbane by Software4Business. We've spent more than 25 years implementing ERP systems for wholesalers, distributors and manufacturers, and Cin7 Core is what we do every day.
So Cin7Flow follows Cin7's rules instead of fighting them: it checks before it creates, it keeps a record of everything it sends, and it shows you exactly what it did.
Simple pricing.
Flow setup from US$1,500, then hosting and monitoring for US$199 a month per flow, including support time. US dollars, including GST, quoted before we start.
FAQ
Questions suppliers ask first.
Does Cin7Flow work with DEAR Inventory?
Yes. Cin7 Core is the new name for DEAR Inventory (DEAR Systems). Cin7Flow connects through the Cin7 Core API, so if you log in to Cin7 Core today, it works with your account.
What happens when an order has a problem?
It's held, not lost. The order waits in Pending with a plain-English reason, like a SKU that isn't in Cin7 or a price outside your tolerance, and the right person gets an email. Fix the cause, press Try again, and it goes through.
What if a partner sends the same order twice?
Cin7Flow compares the resent file with the sale already in Cin7. If nothing changed, it's filed quietly. If something changed, it waits for you with the differences listed, and you choose: void the original and import the new one, import it as a second sale, or ignore it.
How long does it take to go live?
Most flows are live within two to four weeks. Most of that time is testing with real files and waiting on the partner's server details, not building.
Show us a partner file. We'll show you the flow.
Bring a sample order or invoice file to a 30-minute call and we'll walk you through how it would land in Cin7 Core, and what goes back to your partner.