Catalogue and checkout live together
Products, pricing, and customer payment flow stay linked so the shell behaves like an operating system, not a storefront wrapper.
YionCommerce
Sell online and in-personone stock, one set of numbers.
Storefront, inventory, bookings, multi-channel POS. Every sale flows into your ledger and your CRM in real time. Stock-outs become tasks, not surprises.
Products and services in one shellCheckout and deposits connectedInventory and orders stay aligned
Channels
Web · POS · Marketplaces
Payments
Stripe + GoCardless
Sync
Real-time to ledger
Illustrative preview
Commerce board
Orders, stock, and delivery posture
Open orders
21
Low stock
5 SKUs
Catalogue
2Summer kit
Live
Consultation package
Bookable service
Orders
2#1042
Processing · £240
#1043
Shipped · £88
Inventory
2Warehouse A
2 lines below threshold
Warehouse B
All clear
Bookings
1Tuesday slots
3 deposits due
Purchase order suggested
Stock signal
One fast-moving SKU has crossed the reorder point and is ready for ops review.
Why operators switch
Catalogue, checkout, stock, and service delivery stop drifting apart.
Orders and returns stay operational
Fulfilment, returns, and order-state movement remain visible without splitting ops between channels.
Inventory and suppliers belong to the same thread
Low-stock signals, warehouses, purchase orders, and suppliers sit beside live catalogue activity.
Services and booking deposits are not an afterthought
Commerce can carry service businesses too, with bookable services and deposits feeding the same revenue stack.
Revenue thread
From product listing or service slot to paid order, one revenue thread.
Define what the business sells, take payment or deposits, then carry fulfilment, stock, and supplier work in the same shell without rebuilding context.
Merchandise or service catalogue
Keep products, services, and pricing in the same shell the team uses to run orders and stock.
ProductsServicesPricing
Take payment or deposit
Checkout, card flows, and booking deposits stay tied to the revenue object that created them.
CheckoutStripeDeposits
Fulfil, return, and reorder
Carry order operations into stock movements, returns, supplier work, and purchase orders from one place.
OrdersInventoryPOs
Revenue lane
Northbridge Goods and Services
Active lines
38
Products + services
Open ops
9
Orders, returns, or POs
Sell from one catalogue
Products and services start from the same commerce shell rather than branching into separate back offices.
Take payments cleanly
Checkout sessions and booking deposits stay linked to the thing the customer actually bought.
Operate the back end
Inventory, suppliers, returns, and replenishment remain part of the same revenue thread.
Ops control
What needs attention
Returns backlog
Low stock queue
POs awaiting approval
Revenue mode
How the shell sells
Online checkout
Service deposits
Order progression
Inside the shell
The commerce surfaces that keep operations close to the sale.
This shell already exposes catalogue, orders, checkout, inventory, suppliers, purchase orders, returns, and booking flows as connected workspaces.
StorefrontInventoryBookingsPOSChannelsPaymentsOrdersReports
Catalogue and product publishing
Create and maintain products or services from the same shell that drives checkout and operations.
CataloguePricesPublishing
Order desk and fulfilment
Move orders from confirmation through delivery while keeping customer, total, and status visible in one place.
OrdersStatusFulfilment
Checkout and payments
Monitor checkout flow and keep online payments close to the order or deposit they belong to.
CheckoutPaymentsAbandonment
Inventory and warehouses
Track low stock, warehouse context, and availability without breaking catalogue control into another app.
InventoryWarehousesLow stock
Suppliers and purchase orders
Keep sourcing, vendor contacts, and incoming stock organised in the same operating shell.
SuppliersPOsReceiving
Returns and bookable services
Protect aftercare and service delivery with returns handling plus booking and deposit visibility where it belongs.
ReturnsBookingsDeposits
Rollout and control
Run products, services, or both without splitting the back office.
Some businesses just need a cleaner online order desk. Others need stock rooms, suppliers, or bookings. The shell can expand with the operation.
Storefront and checkout
Best when getting products live and taking payment cleanly is the immediate win.
- Catalogue
- Checkout
- Online payment
Stockroom and supplier control
Best when operations need tighter grip on availability, warehouses, and replenishment.
- Inventory
- Warehouses
- Purchase orders
Service and bookings lane
Best when the business sells time, appointments, or deposits as part of the same revenue model.
- Services
- Bookings
- Deposits
Commerce record
Northbridge Commerce
Catalogue, order, and stock context linked
Order posture
Open orders
21
Returns
2
Ops note
Three orders can ship now and one SKU is ready for a replenishment decision.
Timeline
Recent shell activity
Catalogue
New service package published alongside physical stock.
Checkout
Payment captured on the latest order batch.
Inventory
Warehouse threshold triggered a low-stock alert.
Bookings
Upcoming appointments show two unpaid deposits.
Why it lands better
A commerce shell built for the operation behind the sale.
Order operations
Typical stack
Checkout is polished, but fulfilment and returns break into separate tools immediately.
YionCommerce
Order status, returns, and operational follow-through stay in the same shell as the sale.
Stock control
Typical stack
Inventory and warehouses are often a second system the team has to keep in sync manually.
YionCommerce
Low-stock, warehouse, supplier, and PO surfaces sit beside live commerce activity.
Services and products
Typical stack
Businesses that sell both usually end up with separate tools for each side.
YionCommerce
Products, services, bookings, and deposits can live in the same revenue shell.
Aftercare
Typical stack
Returns and customer resolution often get pushed into inboxes and spreadsheets.
YionCommerce
Returns stay visible as part of the commerce operation itself.
Revenue continuity
Typical stack
Payments, orders, stock, and customer context rarely stay aligned after checkout.
YionCommerce
The shell keeps revenue objects and operations close from first order to final fulfilment.
Launch lanes
Choose the commerce rollout lane that matches how the business sells.
Online store launch
Best when a product business needs catalogue and checkout running fast.
- Products
- Checkout
- Orders
Operations and inventory
Best fitBest when availability, suppliers, and replenishment are where margin gets lost.
- Inventory
- Warehouses
- Purchase orders
Hybrid products and services
Best when the business needs storefront, bookings, and deposits under one roof.
- Services
- Bookings
- Deposits
Practical note: product sellers, service businesses, and hybrid operators can expand within one shell rather than replatforming every time the business model broadens.
Common questions
The questions buyers ask before they switch.
- Can I migrate from Shopify?
- Yes — products, variants, customer list and order history come across. Custom storefront themes get re-themed to YionWebsite blocks.
- Do you support marketplaces?
- eBay and Amazon are on the integrations roadmap (Phase 2). For now, web storefront + POS + booking is the day-one surface.
- How are taxes handled?
- Stripe Tax is wired in for the storefront — automatic UK VAT, EU OSS, US sales tax. POS uses your VAT scheme from YionLedger.
Final CTA
Run the shop and the books from one screen.
Every YionCommerce sale lands in YionLedger and YionCRM in real time. No more end-of-month spreadsheet shuffles.
Ops queue
6 commerce moves ready now
Low-stock review
One SKU crossed reorder threshold this morning.
Return approval
Aftercare decision needed on the latest return request.
Booking deposit chase
Three service slots still need deposits before delivery.
Commerce signal
Today
Orders
21
Deposits due
3