How to Automate Cin7

Cin7 is the one honest count of what a business owns

Cin7 is cloud inventory management software, sold in two editions: Cin7 Core for businesses that want the standard set working out of the box, and Cin7 Omni for the ones with a shape nobody else has. It sits underneath retailers, wholesalers, small manufacturers and the brands that sell in four places at once.

Its job is to be the single count. A product exists in a warehouse, on a shelf in a shop, on a Shopify page, in a marketplace listing and on a purchase order that has not landed yet. Without one system holding all five, the business ends up selling stock it does not have, or holding stock it forgot about.

That makes it unusually consequential for a piece of back-office software. A wrong number in a spreadsheet is embarrassing. A wrong number in the stock file is a cancelled order, a chargeback, or a production run that stops.

Every purchase order turns into a week of asking

Raising the order is the quick part. Finding out what happened to it is the job.

The purchase order goes to a supplier who acknowledges it by email, or does not. Somebody logs into the supplier's own portal to see whether it shipped, and gets a status that means something slightly different at every supplier. Somebody opens the freight forwarder's tracking page to find out when the container actually arrives, then updates the expected date in Cin7 by hand. Somebody checks the 3PL's portal to confirm what was received, because the receipt has not come through yet and the stock is still showing as on the water.

Then it happens again next week, for the next forty orders.

None of it is difficult. It is a person, five logins and an afternoon, repeated for as long as the business keeps buying things. And when it slips, the stock file quietly stops being true, which is the one thing it was for.

Cin7

Arrival dates that match the supplier The real ship date read off each supplier's own portal and written back, so the expected arrival in Cin7 is the one the supplier is working to.

Lead times measured, not guessed What each supplier promised against what each supplier delivered, tracked over time so the reorder point rests on a true number.

Chargebacks found before the remittance Retailer vendor portals checked for short-ship claims and deductions, with the dispute window on each one still open.

ForesightAI forecasts the demand, it cannot confirm the shipment

Cin7 automates the ordering side properly, and it is worth setting up before adding anything around it.

Reorder points can be set per product and per location, and once a supplier and a supplier price are attached to a product, Cin7 will generate the purchase order itself. Reorder suggestions go further and take lead time and demand into account rather than a flat minimum. ForesightAI forecasts demand so the buying is planned against what is likely rather than what happened last month. The Automations module sends notifications on orders, sales, inventory and suppliers to whoever needs to know.

The pattern is that all of it works on numbers already inside Cin7. That is a real ceiling, and it shows up in the same place every time.

The lead time in the supplier record was typed in by somebody two years ago. The expected arrival date is whatever the last person to check the forwarder decided to enter. The stock the 3PL actually holds is whatever the last sync said. Every one of those facts has a live version, and every live version is on a website Cin7 has no connection to.

Stock levels that account for what has not landed yet

An expected arrival date can be the supplier's own date rather than somebody's guess from two months back.

Every open purchase order checked each morning on the supplier's own site, with the real ship date written back so the expected arrival in Cin7 matches the one the supplier is working to. Container ETAs read from the forwarder and applied to the lines they cover, so a slip of two weeks becomes a stockout risk you can still air-freight around.

Lead times measured rather than assumed: what each supplier promised against what it actually did, over the last twenty orders, so the reorder point rests on a true number.

The same reach covers the other end. The 3PL's portal read to confirm what was received against what was sent. The retailer's vendor portal checked for chargebacks and short-ship claims before they turn up on a remittance. Marketplace listings checked against the stock file, so nothing stays live when the shelf is empty.

Keep the boundary at the point money moves. Reading a portal and updating a date is safe to leave running. Placing a purchase order, or emailing a supplier about a late shipment, should be drafted and read by a person.

Confirming a delivery date is not planning

Deciding how much to buy is judgement, and it should stay with the person who knows the business. Finding out whether the last order shipped is not.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens the supplier portal, the forwarder's tracking page or the 3PL's site, reads what is on the screen, and writes it into Cin7 or the sheet your planning meeting works from.

It runs on your schedule in your own private environment, and you can watch a run and stop it. Anything that places an order or messages a supplier is drafted and waits.

The workflows below are already built, and each one names the systems it opens.