The Spreadsheet Behind the Shopfront: How Product Businesses Finally Get Control of Their Operations

The Sunday Night Ritual

Zara runs a wholesale homewares business out of a warehouse in Melbourne's outer east. She sources from six suppliers across three countries, sells to about 140 retail accounts, and ships direct-to-consumer through her online store. By any measure, the business is working. Revenue is solid. Customers come back.

But every Sunday night, without fail, she sits down with three browser tabs open, a coffee going cold beside her, and a spreadsheet that she has been patching since 2021. One tab is her Xero. One is her Shopify admin. One is a Google Sheet where she tracks what she owes suppliers, what landed costs she paid on the last shipment, and which retail accounts are overdue.

She spends roughly four hours on this ritual. Every week. Not because she enjoys it. Because if she doesn't, something falls through the cracks. A supplier invoice gets missed. A retail account gets chased twice, or not at all. A product that cost more to land than she realised quietly eats into her margin.

Zara is not disorganised. She is running a genuinely complex operation on tools that were never designed to talk to each other.

The Product Business Problem Nobody Talks About

There is a version of the "too much admin" story that gets told a lot in service businesses. Consultants, tradies, agencies. The narrative is familiar: the owner is so buried in timesheets and invoices that they stop winning new work, and the business slowly stagnates.

Product businesses have the same problem, but it looks different. The admin isn't just invoicing. It's the entire chain from supplier to customer, and every link in that chain generates its own paperwork, its own data, its own reconciliation task.

You have purchase orders going out to suppliers. You have landed cost calculations that need to account for freight, duty, and currency conversion. You have stock that needs to be tracked across locations. You have retail accounts with credit terms, payment histories, and reorder cycles. You have an online store generating orders that need to be fulfilled, invoiced, and reconciled against what actually shipped.

Each of those functions has a "best of breed" tool someone will recommend. Shopify for the storefront. Xero for accounting. A separate CRM for your wholesale accounts. A spreadsheet for supplier management. Maybe a tool like Cin7 or Dear for inventory if you've grown enough to justify it. And then, because none of these tools share data natively, you spend money on Zapier integrations or you hire someone to manually reconcile them.

The result is a business that runs, but only because someone is constantly filling the gaps between systems. Usually the owner.

What "Connected" Actually Means

The word "integrated" gets used a lot in software marketing, and it has been stretched so thin it barely means anything anymore. Most of the time, "integrated" means two separate databases that send each other updates on a schedule. When the sync works, it's fine. When it doesn't, you have duplicate records, missing data, and an afternoon of cleanup ahead of you.

Opus takes a different approach. Everything sits in one database. Not one dashboard that pulls from multiple databases. One actual database, where your clients, your projects, your finances, your supplier records, and your team communications all share the same data model.

For a product business, this matters in ways that are hard to appreciate until you've experienced the alternative. When you update a supplier's payment terms, that change is reflected everywhere, immediately, because there is only one record. When a retail account's contact details change, you update it once. When a product's cost changes because a supplier raised their prices, the impact flows through to your margin calculations without anyone needing to manually update a spreadsheet.

This isn't a technical detail. It's the difference between spending Sunday nights reconciling data and spending Sunday nights doing something else.

Supplier Management Without the Spreadsheet

For most product businesses, supplier management is a spreadsheet with columns that have grown over the years. Lead times. Minimum order quantities. Payment terms. Contact names. Currency. The last order date. Whether the last shipment had quality issues.

This information lives in a spreadsheet because there was never a better home for it. CRM tools are built for customers, not suppliers. Accounting tools track what you owe, but not the relationship context. Project management tools aren't designed for procurement cycles.

In Opus, suppliers can be managed as contacts within the same CRM layer that handles your customers. You can attach notes, track order history, log communications, and link supplier records directly to the purchase orders and invoices associated with them. When you're looking at a product's cost history, you can see which supplier it came from, what you paid, and what the landed cost was after freight and duties.

This isn't a dedicated inventory management system, and Opus doesn't pretend to replace something like Cin7 for businesses running complex multi-location stock operations. But for the majority of product businesses, the supplier management problem isn't a software capability problem. It's a data fragmentation problem. The information exists. It's just scattered across three tools and a spreadsheet.

Cost Tracking That Reflects Reality

Here's a margin problem that almost every product business owner recognises. You set your prices based on your cost of goods. Your cost of goods is based on what you paid the supplier. But what you actually paid, once you account for freight, import duties, currency conversion at the time of the order, and the cost of any quality failures, is often meaningfully different from the invoice price.

Most businesses track this in some form. But they track it in a spreadsheet that doesn't connect to their accounting software, which doesn't connect to their sales data. So when someone asks "what's the actual margin on this product line", the honest answer is usually "I think it's around X, but let me check the sheet."

Opus's financial layer is built around real-time cost visibility. Because timesheets, expenses, supplier costs, and revenue all feed into the same system, you can see what a product or a client relationship is actually costing you, not what you estimated it would cost when you set your prices.

For product businesses, this means being able to look at a wholesale account and see not just what they've ordered and paid, but what it cost to service that account. Freight. Returns. Time spent on their account by your team. The picture that emerges is often different from the one that lives in your head.

Invoice Management Across a Mixed Revenue Model

One thing that makes product businesses operationally complex is that they often run multiple revenue models simultaneously. Direct-to-consumer sales through an online store. Wholesale accounts on 30-day terms. Maybe a subscription box or a recurring order arrangement with a few key accounts. Possibly some B2B custom orders that are essentially project-based.

Each of these models generates invoices differently. The online store creates transactions automatically. Wholesale accounts need invoices raised manually or on a schedule. Custom orders might have deposit and balance invoices. Managing all of this across different tools means someone is constantly moving data between systems.

Opus connects to Xero with a two-way sync, which means your invoicing and reconciliation happens in a tool your accountant already knows. But the client records, the order history, and the communication history all live in Opus, connected to the financial data rather than sitting in a separate CRM that only talks to Xero when the sync runs.

For a business like Zara's, this means her wholesale accounts are managed in one place. She can see a retail account's order history, their outstanding invoices, any notes from the last conversation her sales rep had with their buyer, and their payment behaviour, all without switching tools.

The CRM Layer That Most Product Businesses Skip

Wholesale and B2B product businesses often have a CRM problem they don't fully recognise as a CRM problem. They know their key accounts well. They have relationships. But those relationships live in the account manager's head, or in their email inbox, or in a notes app on their phone.

When that account manager leaves, or when the business grows to the point where one person can't hold all the relationships, things get fragile. Accounts feel neglected. Reorder conversations don't happen at the right time. A competitor gets in because nobody noticed the relationship had gone quiet.

Opus's CRM layer is designed to make relationship context visible and shared. Not just contact details, but the full history: what they've ordered, what conversations have happened, what's outstanding, what was promised. For a product business managing 50 or 150 wholesale accounts, this is the difference between a sales process that depends on individual memory and one that the whole team can contribute to and rely on.

This matters even more as the business grows. The founders of most product businesses are excellent at relationships. The challenge is building a business where those relationships don't depend entirely on the founder being in every conversation.

Reporting That Doesn't Require a Spreadsheet

At the end of a quarter, most product business owners want to answer a handful of questions. Which product lines are actually profitable? Which accounts are growing, and which are quietly shrinking? What's the landed cost trend on our main supplier? Are we collecting on time?

Getting answers to these questions, when your data is split across Shopify, Xero, a CRM, and a spreadsheet, takes hours. You export from one system, paste into another, build a pivot table, realise the date ranges don't match, start again.

Opus's reporting draws from the single database that holds all your operational data. You can ask questions in plain language using the AI business intelligence layer, or build reports that pull from financial, client, and operational data simultaneously. The answers are current because the data is current, not because someone ran an export this morning.

For business owners who make decisions based on gut feel because getting accurate data takes too long, this changes the quality of the decisions being made. Not because the software is clever, but because the information is actually accessible.

The Admin Spiral in Product Businesses

There's a pattern that shows up in product businesses that have grown past the founder-does-everything stage. In the early days, the founder knows every supplier, every key account, every product's margin. The business runs on their knowledge.

As it grows, that knowledge needs to be distributed. Systems need to carry what the founder used to carry in their head. If the systems aren't there, the founder just works harder. More hours. More Sunday nights. More time spent on administration and less time spent on the things that actually grow the business: finding new accounts, developing new products, building supplier relationships that give you better terms.

This is the admin spiral in its product business form. The craft, in this context, is the product itself and the commercial relationships around it. The business development is finding new accounts and new categories. The administration is everything else. When the administration expands to fill the available time, the craft suffers and the business development stops.

The businesses that break out of this pattern are usually the ones that build systems before they need them, not after. The ones that wait until the pain is unbearable often find that by then, the data is so fragmented and the habits so entrenched that the migration feels impossible.

Starting the Conversation

Opus isn't a replacement for a dedicated inventory management system if your operation genuinely needs one. It's also not a replacement for Shopify if your e-commerce storefront is a core part of your business. What it replaces is the connective tissue between those tools: the spreadsheets, the manual reconciliations, the CRM that doesn't talk to your accounting software, the supplier records that live in someone's inbox.

For product businesses that are spending too much time moving data between systems and not enough time on the work that actually grows the business, it's worth understanding what a unified operational layer would actually change.

Opus has a free tier for smaller teams, and the pricing scales with the size of your operation. If you're curious about what it would look like for your specific setup, the features page at [opus.net.au](https://opus.net.au) is a reasonable place to start.