Field Analysis

Cin7 without a storefront: middleware and operations-only builds

Most writing about Cin7 and commerce assumes a storefront is being built. Often there isn't one. A business might be coming off spreadsheets and need an accurate stock position before it needs a website, or it might already have a storefront and need Cin7 in the middle, moving orders and inventory between systems that all exist. Both are real projects, and both get mis-scoped when the conversation starts with a platform.

What does a Cin7 project with no storefront look like?

The first is the seller coming off spreadsheets and email. Stock lives in one person's workbook, orders arrive by email and phone, and the business has grown past the point where that holds. Cin7 markets this directly as moving off spreadsheets, and it's the most common entry point into the product. There's no website in this project. There's a data migration, a set of process decisions, and a period of getting counts trusted.

The second is Cin7 as the middle layer. The business already sells somewhere, maybe a Shopify store, maybe a marketplace, maybe both, and it already has an accounting system and possibly a 3PL. What it doesn't have is one place where all of that agrees. Cin7 goes in the middle and owns the operational record while every existing system keeps doing its job.

The third is wholesale and retail supply with no direct-to-consumer channel at all. Orders arrive by EDI from big-box retailers, or by purchase order from trade accounts, and the buying experience is a relationship, not a website. Cin7 handles the inventory, the orders, and the compliance around them.

What does an operations-only project involve?

The work moves from design and front-end build to data and process, and the sequence matters more than in a storefront project because everything downstream depends on the counts being right.

1. Product data first – SKUs, units of measure, variants, suppliers, and cost. This is where the time goes, and shortcuts here surface later as reorder points that don't work.
2. Locations and rules – Warehouses, bins, and the rules for moving stock between them. Multi-location is where Cin7 earns its keep, and decide it early instead of discovering it late.
3. The first stock take – Not a task, a milestone. Until the counts are trusted, nobody uses the system for decisions, and the project hasn't landed.
4. The ledger connection – Cin7 to Xero or QuickBooks, and a month that reconciles. That's the test of whether the setup was done properly.

Where's the work when Cin7 sits in the middle?

Cin7 publishes native connectors for the storefronts and marketplaces most businesses already use, so the middle-layer build is often less custom than people expect. Where it gets specific is in the surrounding systems: a 3PL that needs stock and fulfilment status both ways, EDI trading partners with their own document requirements, and the accounting system's expectations about how and when a sale becomes a journal entry.

The failure mode is the same one that spoils storefront projects. If any system in the chain keeps its own stock number, the middle layer has no authority and you've built a synchroniser, not a source of truth. Cin7 holds the position, everything else reads it.

How do you tell which project you're in?

One question does most of the work: is the way a customer buys from you changing? If yes, there's commerce in the project and the storefront decision matters. If no, then nothing a customer sees is changing and the work is entirely inside operations, which means the people to involve are the ones who count stock and close the month, not the ones who care about the buying experience.

Getting that wrong in either direction is expensive. A commerce partner scoping a storefront for a business that needed a stock take is the obvious version. The quieter version is an operations project that quietly needed a buying experience, discovered at the point the sales team asks why customers still phone in orders.

What to take from this

1. A lot of Cin7 projects have no website in them – Coming off spreadsheets, running Cin7 in the middle, and wholesale or EDI supply are all common and all storefront-free.
2. Stock takes are milestones, not tasks – Until the counts are trusted, nobody makes decisions with the system and the project hasn't really landed.
3. The middle layer needs authority – If any connected system keeps its own stock number, you've built a synchroniser instead of a source of truth.
4. Ask whether buying is changing – That single question sorts an operations project from a commerce one, and it decides who should be in the room.

For what Cin7 runs and where accounting sits, start at the Cin7 ecosystem hub. For who owns which part of the work, see scoping a Cin7 project.

Frequently Asked Questions

Next Step

Get the foundation right before you build.

For readers scoping a platform decision or wanting a full architecture recommendation.