Stock Management System: Inventory, Invoicing and a Storefront That Actually Launches

The Challenge

Small merchants rarely fail at selling. They fail at the seams between tools: stock in a spreadsheet, invoices in an accounting package, an online store on a third platform and customer details scattered across all three.

Three jobs, one dataset

Inventory, invoicing and an online store all describe the same products, prices and customers. Kept in separate tools, the catalogue drifts. A price change in the shop never reaches the invoice, and an online stock adjustment never reaches the shelf count.

Merchants are not web developers

A business owner can pick a theme and upload a logo, but cannot be expected to know that an unpublished theme means customers still see the old site, or that a missing domain setup silently costs sales. The product had to carry that knowledge for them.

Going live is risky

Once a storefront is public, every gap becomes a customer-facing defect: a placeholder policy page, a missing social preview, a checkout that accepts orders it cannot take payment for. A publish button without safeguards is a liability.

Shared workspaces need accountability

When several staff members can change prices, policies and payment settings, knowing who changed what, and when, becomes essential.

Payments are a stack, not a switch

Stripe and PayPal each involve accounts, keys, webhooks and activation. Presenting that as a single toggle produces merchants who believe they can accept cards when they cannot.

Our Approach

• Treat the storefront like shipped software. Themes carry a version, a publication state and an "unpublished changes" flag, with preview and publish as separate actions, so a merchant gets a staging workflow without needing to know the term.
• Gate publication on readiness. Before a store can go live, the platform checks domain status, theme publication, mobile responsiveness, social preview, contact details and store policies. Blockers are blockers, not suggestions.
• Make SEO a first-class feature. A store with no metadata is invisible, so every store gets a complete SEO surface with a live search preview.
• Show integration status honestly. Payments state whether each gateway is merely connected or fully activated.
• Log every field change. Every edit records who made it, where, when, from which IP and what changed.

What We Built

A multi-tenant commerce workspace with a back office and a public storefront.

• Back office. Dashboard, inventory, customers, invoices, staff roles, notifications, activity logs, settings and billing, with a workspace switcher and subscription status.
• Analytics dashboard. Completed and cancelled orders, low-stock alerts, open order value, revenue, SKU and customer counts, invoice status, best sellers, most-discounted items and top revenue categories.
• Storefront administration. Launch readiness, themes, navigation, pages, products, collections, orders, branding, payments, checkout and SEO, all managed from one Website section.
• Launch readiness checklist. A single pre-flight view with pass or fail states and a direct route to fix each item.
• Branding system. Logo, favicon, colour tokens and typography with a live storefront preview.
• Page manager. Templates, published, draft and unpublished states, index control and visibility settings.
• SEO controls. Search preview, meta title and description, canonical URL, robots directives, organisation structured data, business details and site verification.
• Payments and checkout. Separate readiness states for Stripe and PayPal, cash on delivery as a first-class method, multi-currency invoicing defaulting to PKR and tax settings.
• Activity log. Colour-coded, field-level before-and-after diffs with actor, page, timestamp and IP address.
• Public storefront. Each merchant's store is served at its own path or a custom domain, with its own theme and CMS pages.
• Safe onboarding. A demo-data generator lets new merchants explore without risk.

Design Decisions

The back office uses a dark interface with a persistent navigation rail, designed as a daily working tool rather than a website. The sidebar mirrors how merchants think, from Inventory, Customers and Invoices through Website and Staff.

The launch-readiness view is the most valuable screen in the product. It turns the open-ended task of "setting up a store" into a finite checklist a non-technical owner can actually complete.

The Results

What started as a stock management tool grew into a full commerce platform.

• One catalogue, three jobs. Inventory, invoicing and the storefront share one data model, ending the drift that comes from running separate tools.
• Fewer failed launches. Readiness gating stops merchants from believing they are live while a domain, theme or policy page is missing.
• Safer everyday edits. Draft theme changes cannot reach customers, so routine updates carry no risk.
• Discoverable from day one. A complete SEO surface means new storefronts are not invisible by default.
• Accountable teams. Field-level audit logging lets owners delegate price and policy changes to staff with confidence.
• No phantom payments. Honest gateway states prevent merchants from taking orders they cannot process.

Themes are versioned, publishing is gated, SEO is configurable, payments tell the truth about their own state and every change is attributed to a person. That platform thinking is what turns a stock system into software a business can grow on.