What Is a Connected Commerce Stack — and Does Your Business Need One?

“Technology stack” sounds like terminology that belongs inside a software company. But almost every modern business has one. Most just don't call it that.

Your EPOS is part of it. Your card terminals are part of it. Your website is part of it. Your payment gateway, bank account, inventory system and accounting software can all be part of it.

Together, these systems form your commerce stack. The important question is whether they work together.

A commerce stack is simply the collection of technology a business uses to sell and operate. For an independent retailer, that might include:

There may be additional components for CRM, loyalty, bookings, purchasing, delivery, marketplaces or automation.

The objective is not to have every component. It is to have the components your business actually needs.

A connected stack allows useful information to move between systems rather than requiring employees to repeatedly move it themselves. Take a sale. In an ideal workflow, that single event might:

• record the transaction,
• trigger the correct payment,
• reduce stock,
• update relevant sales channels,
• contribute to reporting,
• settle into the appropriate account,
• and ultimately reach the accounting system.

Not every business needs that entire chain automated. But each manual handoff should exist for a reason.

Businesses are frequently sold technology based on features. AI-powered this. Cloud-based that. Hundreds of reports. Dozens of integrations.

But software doesn't create value simply by possessing functionality. It creates value when the functionality solves an operational problem.

For many independent businesses, the ideal commerce stack might actually be relatively simple:

• A good EPOS.
• Integrated payments.
• A properly connected website.
• Reliable stock information.
• Clear settlement.
• Straightforward accounting.

That's enough. The objective isn't maximum technology. It's minimum friction.

Banking deserves particular attention because it sits at the end of the commercial journey. A business can optimise the customer-facing parts of commerce while leaving the movement of money fragmented behind them.

But payments, settlement and banking are closely connected operationally.

• How quickly does money arrive?
• Where does it arrive?
• Can the owner understand which sales produced each settlement?
• How easily can those transactions be reconciled?
• Can that information reach accounting software without unnecessary work?

Thinking about banking as part of the commerce stack allows those questions to be considered during system design rather than afterwards.

This is one of the biggest misconceptions around commerce transformation. A connected stack does not require ripping everything out and starting again.

• If you already have an excellent accounting system, keep it.
• If your EPOS perfectly matches your operation, keep it.
• If employees understand the current inventory system and it works reliably, there needs to be a good reason to replace it.

Connections should be explored before replacements. The best technology project can sometimes involve changing surprisingly little.

Replacement becomes more reasonable when a system creates a genuine constraint.

• Perhaps it cannot integrate with anything else.
• Perhaps it forces excessive manual work.
• Perhaps it prevents the business adding an important sales channel.
• Perhaps it is expensive relative to what it provides.
• Perhaps it no longer matches the way the business operates.

The decision should follow the problem. Not the other way around.

Before evaluating technology, Node Commerce reduces the problem to three broad outcomes.

If changing a system doesn't materially improve one of those areas, there needs to be a very good reason for changing it.

You already have a commerce stack. The real question is whether it has been designed or merely accumulated.

Most businesses add technology gradually.

• A till today.
• A website two years later.
• A different payment provider.
• Accounting software recommended by the accountant.
• A stock spreadsheet somebody created because the other systems didn't quite work.

Individually, every decision may have been sensible. Collectively, they may no longer form the best system.

That is why optimisation should start by looking at the complete operation rather than selling another isolated product.