Everything between your partners and Cin7 Core.

Purchase orders and drop-ship orders are collected from your partner's server and raised as sales in Cin7 Core, with the partner's order number on the sale.

• Collected over SFTP (password or private key), FTP or FTPS
• JSON and CSV files, each partner read through its own field map
• Created as draft during a parallel run, then authorised once you're live
• Your price tier, or the partner's prices within a tolerance you set
• Pick, pack and ship left to your warehouse, or done automatically
• Drop-ship orders delivered to the end customer's address
• Processed files moved to a processed folder, duplicates to their own folder

On your schedule

• Every few minutes, once a day at a set time, or only when you press Run
• Run now from the dashboard whenever you want to check straight away

The return leg is easy to forget and is often half of an integration. Cin7Flow reads invoiced sales from Cin7 and writes them in the format your partner expects, to the folder they collect from.

• JSON, CSV or pipe-delimited, matched exactly to the partner's specification
• Only the customers and invoice statuses you choose
• Held until the goods are despatched, when the file needs to carry tracking
• A cancellation file when a sent invoice is voided in Cin7
• The sale marked in Cin7 once sent, so anyone can see it went
• Remembers how far through Cin7 it has read, however long it was switched off

Moving files between servers

• Copy files from one SFTP or FTP folder to another on a schedule
• Nothing is moved or deleted at the source until the copy is confirmed

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

Nothing is lost and nothing goes into Cin7 half right. When an order doesn't fit, it waits in Pending with a plain-English reason and the right person gets an email.

• A SKU that isn't in Cin7: hold the order, import and warn you, or create the product with your defaults
• A price outside your tolerance: hold the order, or import it and warn you
• A customer over their credit limit: hold the order, or import it as a draft
• Fix the cause and press Try again. The order picks up where it stopped
• Edit the order in a simple form: lines, quantities, prices and charges

Resent orders

• Every resent order is compared with the sale already in Cin7
• Identical? Filed quietly and shown in the log
• Different? Held with the changed lines listed, and an email to you
• Choose: void the original and import, import as a second sale, or ignore

Your partners don't use your codes. Cross-references translate theirs to yours, and your team can keep them up to date without calling us.

• SKUs: the partner's product number to your Cin7 SKU
• Customers: store or branch numbers to Cin7 customers
• Locations: the partner's warehouse codes to your Cin7 locations
• Tax: the partner's tax codes to your Cin7 tax rules
• One list per flow, used every time an order arrives

Moving warehouses, adding a location or re-binning a store? Doing hundreds of stock transfers one by one in Cin7 takes days. Upload a spreadsheet instead.

• Excel or CSV: from location, to location, SKU and quantity
• Optional bins, batch numbers, expiry dates, references and comments
• One Cin7 stock transfer per row, created as draft, in transit or completed
• Upload on the dashboard, or drop the file in an SFTP or FTP folder
• A row with a problem is held on its own, fixed and sent again
• Download a ready-made template from the dashboard

Silence means healthy. You hear from Cin7Flow when a person needs to do something, and once a day with a summary of what it handled for you.

• Business alerts (a price, a SKU, a credit limit) to the address set on each flow
• Technical faults (a server or Cin7 unreachable) come straight to us, so we can fix them
• A daily summary email each morning
• Every file's full history: collected, checked, delivered, archived
• An operations log of every settings change and who made it

Your team gets its own login to see every flow, every file and every decision waiting for them. The parts that keep orders flowing stay with us.

• Card or grid view of your flows and connections
• Pause, restart or run a flow now
• Update a connection's password or key when it changes
• Edit cross-references and fix held orders
• Forgotten passwords reset by email
• See the integrations catalogue and ask for a new flow

Your partners trust you with their orders. Cin7Flow is built so that trust holds.

• Hosted on Fly.io servers in Sydney, with the database in the same region
• Passwords and API keys encrypted before they're saved, and never shown again
• Each client sees only its own flows, files and logs
• A fixed outgoing IP address your partners can whitelist
• Updates done with flows on hold, so nothing is half-processed
• Regular database backups