Skip to content
Digital Discovery Group
Syd Sign in
The platform

Meet Jamtable.

An AI commerce workspace built out of twenty years of operational pain, by the person who felt it. The tools we needed as operators did not exist, so we wrote them. It is not a theme, a template or a reseller badge: every line of it is ours, so when your business needs it to behave differently, we change the software.

One platform for your store and everything behind it.

What this means.

01 Commerce engine

One set of numbers.

Catalogue, stock, pricing, checkout and fulfilment working off the same truth, so the storefront, the counter and the back office never disagree about what you have or what it costs.

02 Advanced merchandising suite

Ranging that answers to sales.

Placement, ranging and promotion driven by what is actually selling rather than last quarter's plan. Products tagged by capability, so a search can answer the question the customer really asked.

03 Personalisation

The store that fits the shopper.

Every visitor sees the version of the catalogue that suits how they shop, and co-purchase intelligence puts the right accessory in front of them at the moment it is relevant rather than in an email three days later.

04 Echo AI chat and email marketing

Answers first, then follow-up.

Echo AI answers from live product, stock and service data and declines when it does not know. Email marketing is triggered by what customers actually do, using the same data the storefront runs on.

The argument

One data model, not a stack.

Anyone running an online store of any size ends up with a stack. A storefront platform, a point of sale, something for stock, a folder of supplier spreadsheets, an app for email, and an accounting package downstream of all of it. Every one of those choices is defensible on its own. Together they produce a business that cannot answer a simple question, such as what a given item has actually cost by the time it reaches a customer, or how much stock is genuinely available to sell right now.

Jamtable was built the other way around. One data model, twelve production databases behind a single API, and every surface reading from the same source. Composable where it needs to be, through a module matrix that lets each business run only the parts it uses. Opinionated where it matters, so money, stock and documents follow a controlled sequence with separation of duties enforced by the platform rather than by staff discipline.

It runs at the edge on Cloudflare, multi-tenant from the first line of code, with AI in the foundations rather than bolted to the side. It was proven first in one of the hardest categories in retail: a motorcycle dealership, where stock is serialised, compliance-bound, financed, traded in and frequently sold before it physically arrives. A platform that holds up under that will not struggle with a catalogue of apparel.

Who it is for

Anything with something real behind it.

Any business with an online store and something real behind it. Stock to count, orders to pick, suppliers to buy from, customers to keep, and money to reconcile.

The value scales with operational complexity. A single online store with one stockroom gets a fast storefront, a clean catalogue and one place to work orders. A business running a shop floor, a warehouse, a purchasing function and a service department gets the whole argument, because those are the parts that normally sit in separate systems and disagree with each other.

Modules are switched on per business through the module matrix. Nobody pays for a workshop they do not have, and nobody is shown a screen they will never open.

Core capabilities

The twelve that carry the argument.

Each one has a headline, what it does, and the concrete capabilities beneath it.

Unified commerce core

One catalogue. One stock position. Every channel.

Every channel reads from the same catalogue and the same stock position, in real time. The storefront, the counter, the pick list and the purchase order are all looking at the same row. Sell an item in store and the web listing decrements before the customer has their receipt. Reserve something online and it cannot be sold twice.

This is the foundation the rest of the platform sits on, and it is the reason the modules below behave as one system rather than as a suite.

  • A single catalogue shared by every channel and every location
  • Live availability by location, stockroom and bin, with allocated, on-order and available held separately
  • One customer record, identical at the counter, in the back office and on the storefront
  • One order spine, so a web order, a counter sale and a staff-entered order are the same kind of object
  • Configuration held in the backend, not in each front end, so a rule changed once applies everywhere
  • Twelve purpose-built databases behind one API, so no module is slowed down by another module's schema
  • Modules switched on per business, so the platform fits the operation rather than the other way round

Storefront and e-commerce

Your website is a view of your business, not a copy of it.

The storefront is generated from the same catalogue, stock and pricing everything else uses, and edited from the same admin. Pages, blocks, media, navigation, theme and SEO all live in the CMS, and per-page SEO completeness scoring tells you which pages are still missing a description before Google does.

Built on Astro at the edge, so pages are fast by construction rather than fast after an optimisation project.

  • Live catalogue with real stock, and complete purchase online, end to end
  • Page builder with reusable content blocks, templates, drafts, publishing states and archive
  • Media library with a shared asset store, and theme, navigation and brand controlled per business
  • Hero sliders, promotional banners and campaign placements scheduled from the marketing calendar
  • Site-wide SEO with per-page completeness scoring across title, description, OG image and canonical
  • Click and collect from any location, and refundable holding deposits where a purchase needs one
  • Google and marketplace feed synchronisation
  • Multi-location storefront with per-location content and opening hours
  • Core Web Vitals treated as a build constraint, not a report

Point of sale

The counter, at counter speed.

The point of sale runs on whatever hardware is already there: iPad, touchscreen, laptop or phone. It is keyboard driven for staff who know what they are doing, and it holds the full catalogue, live stock across every location, and the customer’s complete history in the same screen as the transaction.

Because it is not a separate application talking to a commerce API, there is nothing to reconcile at the end of the day beyond the cash drawer.

  • Full-catalogue terminal with live cross-location stock lookup
  • Customer lookup at the counter, with order and purchase history attached
  • Co-purchase suggestions on add to cart, mined from actual order history rather than manual rules
  • Cash drawer open, count, reconcile, with configurable float, variance tolerance and full drawer history
  • Card and integrated payment handling, and split payment across methods
  • Receipt printing, and digital receipts delivered by SMS as a secure download link
  • Terminal-level security policy, staff sign-in, and per-terminal configuration
  • Configurable order status labels, so the language on screen matches the language on the floor

Order management

One queue, every channel, one set of rules.

Web orders, counter sales and staff-entered orders land in one order spine with one status model. The queue is worked rather than watched: priority is calculated, exceptions are quarantined for review rather than silently failing, and every status change carries an audit entry.

  • Unified order queue across web, counter and phone
  • Order creation wizard for staff-entered and phone orders
  • Priority calculator, so the queue reflects promised dates and pick economics rather than arrival order
  • Quarantine for orders that fail validation, held for a human rather than dropped
  • Separate order streams where a product type genuinely needs a different workflow
  • Discount management with mandatory reason codes, plus discount analytics so margin leakage is visible
  • Order analytics covering value, mix, conversion and cycle time
  • Full audit history on every order and every status transition

Inventory and stock control

Know what you have, where it is, and whether it should be there at all.

Stock is tracked by location, stockroom and bin, with allocated and on-order held separately from available, so the number on screen is the number you can actually sell. Range status classifies the catalogue for buying and reordering, allocation rules decide who gets scarce stock, and stock takes run as a planned workflow rather than a weekend.

  • Live stock positions by location, stockroom, room type and bin
  • Range status classification: core range, ranged, non-ranged, obsolete, with a rules engine to maintain it
  • Reorder thresholds and low-stock alerting per stocked line
  • Stock allocation rules, so committed stock is honoured
  • Inventory adjustments with an approval step and a full activity log
  • Serialised stock tracking with barcode generation and label printing
  • Stock takes: planning, creation, execution, variance review and settings
  • Missing SKU detection, so gaps in the catalogue surface before a customer finds them
  • Product information management across the whole catalogue

Purchasing and suppliers

From reorder point to receipted invoice, in one thread.

Purchase orders are raised from demand rather than from memory. A single register collects everything flagged for reorder across the business, including items other parts of the business are waiting on, and consolidation rules combine them into the smallest sensible number of orders. Supplier catalogues and price files are ingested, cleaned and standardised on the way in.

  • Purchase order creation, tracking, consolidation and consolidation rules
  • A single register collecting every flagged line across the business
  • Purchasing automation, so routine reorders raise themselves against defined rules
  • Supplier directory, onboarding workflow and per-supplier profile management
  • Supplier catalogue and price file ingestion with scheduled import runs and run history
  • Automated supplier image download into owned storage, so product imagery is not hotlinked
  • Discrepancy handling for short, over and damaged receipts
  • Supplier invoices, carrier settings and update process reporting

Warehouse and fulfilment

Routing decided by economics, not by whichever location is closest.

Every line is routed against live stock in milliseconds: which location picks it, who picks it, and how it ships. Pick cost, stock health and promise date all feed the decision, so the system does not empty a profitable location to save a courier leg.

  • Goods receipt against purchase orders, with expected deliveries visible ahead of arrival
  • Zone, aisle and bin location structure, with bulk generation for new sites
  • Pick list generation and picking workflow, sequenced by bin rather than by order
  • Inter-location transfer requests and transit tracking
  • ABC classification, so counting and slotting effort follows value
  • Cycle count scheduling as an ongoing discipline rather than an annual event
  • Consignment tracking for stock held but not owned
  • Ship from store, and pick and pack from any location holding stock

Delivery

Rules a customer can see, and a business can defend.

Delivery is priced and promised by rule rather than by phone call. Postcode zones, product category, condition and value drive both the cost and the estimated window, and the live estimator lets staff and customers see the same answer, because it runs the same rules.

  • Postcode-based delivery zones with per-zone pricing and cut-off times
  • Category-specific delivery rules, so bulky or regulated items follow their own logic
  • Delivery timeframe editor with per-zone estimated windows
  • Surcharge management for remote, oversized and specialist carriage
  • Delivery milestones, so the customer is told where their order is
  • Live estimator for staff and storefront, running the same rules
  • Advanced configuration for carrier selection, exceptions and overrides

Customers, enquiries and loyalty

One customer record, and every conversation attached to it.

Enquiries, live chat, tickets and campaign responses all resolve to the same customer, and the record carries orders, purchase history, saved items and loyalty position. Ticket rules route and prioritise automatically, so nothing sits in a shared inbox waiting for somebody to notice it.

  • Customer directory, profiles, creation and search, with activity across every channel
  • Communications hub covering enquiries, tickets and live chat in one queue
  • Ticket rules for automatic routing, assignment and escalation
  • Live chat with storefront visitors, connected to the same customer record
  • Enquiry analytics and configurable enquiry policy
  • Loyalty programme with tiers, points earn and redeem, expiry, and a customer-facing portal
  • Loyalty analytics covering tier distribution, at-risk members and points liability
  • Saved items and watch lists, giving a direct demand signal on what is not currently in stock
  • Customer tiers driving tiered pricing

Marketing and communications

Every outbound surface in one place, using the customer record you already have.

Campaigns, segments, email, SMS, promotions, pricing rules, reviews and short links, all built on live customer and order data rather than an exported list. A segment is a query against the actual business, so a campaign to customers who have not bought in six months is a segment, not a spreadsheet.

  • Multi-channel campaign planning across email, SMS and loyalty
  • Customer segments built from live order and loyalty data
  • Email marketing with campaigns, contact lists, automations, sender identities, domain authentication, suppression management and deliverability reporting
  • Transactional email templates and inbound webhook event handling
  • SMS via Twilio, with campaigns, transactional templates, lifecycle notifications, digital receipts, and suppression handling for STOP replies under Australian spam regulations
  • Pricing promotions and a promotional calendar, aware of state public holidays
  • Discount reason codes, so every discount is attributable
  • Google Business Profile management and review response templates
  • Recommendations manager, controlling the co-purchase and related product engine
  • Short link management with click analytics, and wishlist shares as demand signals
  • Centralised storefront SEO and newsletter configuration
  • Marketing analytics across campaigns, channels and revenue attribution

ECHO AI

An assistant that can answer, because it is inside the data.

ECHO is not a chat window over a knowledge base. It has direct, permissioned access to the platform’s own data through a large library of configured skills, so it answers operational questions with real numbers and returns work you can act on. Ask it for slow-moving stock by location and it produces a reorder position, not a paragraph about inventory management.

Two assistants, deliberately separated. The internal assistant has full operational access for staff. The customer-facing assistant sits on the storefront with a much narrower surface and no access to operational data.

  • Natural-language operational queries across customers, orders, inventory, finance and performance
  • A large configured skill library giving direct, permissioned access to platform data
  • Retrieval over your own documents, policies and knowledge base, with a managed source list
  • Declines rather than guesses when a question falls outside its knowledge
  • Multi-model routing, so a better or cheaper model can be substituted without a rebuild
  • Cost and usage dashboards, per-model performance, and a full request log
  • Configurable agent settings, guardrails, memory and brand voice
  • Separate internal and public assistants with separate permissions and separate logs
  • MCP surface, so ECHO connects into Claude, ChatGPT or an existing stack
  • AI document classification applied to incoming files

Vertical depth: serialised stock, compliance and finance

Proof that the model holds under load.

Most commerce platforms treat a product as a line with a quantity. That works until the thing being sold is individually identified, legally regulated, financed, traded in, or sold before it physically exists. Jamtable models all of that natively, because the founding business sells motorcycles and none of it was optional.

This matters even if you never sell a vehicle. A platform that carries serial numbers, compliance documents, finance applications, trade-ins and a controlled sale-to-release sequence is not going to be defeated by a catalogue of apparel. It is also the reason the platform suits anyone selling equipment, machinery, appliances, instruments or anything else that arrives with a serial number and leaves with paperwork.

  • Serialised asset register covering new, used, demo and consigned stock across the full lifecycle
  • Separate intake paths per source, each capturing what that path actually needs
  • Registration, VIN and chassis lookup against Australian vehicle data, with results cached
  • Spec taxonomy and attribute management with deduplication tooling, so filtering stays clean at scale
  • Compliance document generation and management
  • A controlled sale state machine from quote to release: deal builder, parked sales, deposits, contract generation and digital signing
  • Finance quoting, pre-approval routing, application tracking and an embeddable repayment calculator
  • Trade-in valuation requests
  • Booking and trial workflows with terms capture, licence capture and configurable policy
  • Competitor pricing comparison against live market listings
  • A release gate, so nothing leaves before funds and paperwork clear

Switch it off if you do not need it. This entire capability is a module. A business selling apparel never sees a compliance form.

Supporting capabilities

The rest of the platform.

Real capabilities, written shorter because they support the argument rather than carry it. Several are module-gated and only appear for businesses that need them.

Service and repair

For any business that fixes what it sells.

Job cards, staff, bays and parts all live in the same system as the sale that created the work. A technician sees their own jobs and can pick up unassigned ones. The board shows what is physically where. Parts on order for a job are visible to purchasing without anybody sending a list.

  • Floor view and bay board, showing every item on site and its state
  • My Jobs, showing a technician their assigned work and the unassigned pool
  • Service requests, check-in and checkout workflow
  • Diary and scheduling against real capacity and skill
  • Technician and bay configuration, controlling who can be assigned what, and where an item sits
  • Service invoicing, drawn from labour and parts consumed on the job
  • Full service history by customer and by item
  • Parts demand from open jobs feeding straight into purchasing

Finance

Money owed, money held, and money owed to you by your suppliers.

The finance module covers the operational money that falls between a commerce platform and an accounting package: receivables, on-account balances, deposits, refunds, supplier rebates and reconciliation. It is not a general ledger and does not try to be.

  • Receivables and on-account balance tracking
  • Payment reconciliation against orders
  • Refund request workflow with approval
  • Accounts payable and cash flow forecasting
  • Supplier rebate programmes, rebate claims and rebate file import
  • Finance fee configuration
  • Separation of duties enforced by the platform: sales staff never record payments, and finance owns deposits from contract signing onward
  • Funds verification gate before high-value goods are released

Documents and compliance

Generated, signed, stored, retained and provable.

Documents are produced from platform data rather than typed, then held under a retention policy with an audit trail against every access.

  • Template builder and reusable document templates
  • Guided document wizard and direct document creation
  • Motorcycle sale document and sale agreement generation and printing
  • Certified document issue and verification
  • File conversion into managed documents, and document merge
  • AI document classification on ingest
  • Document types, categories and approval workflows
  • Retention and disposal policies
  • Full document audit trail
  • Link analytics and document search analytics

Search and discovery

Fast on the keystroke, intelligent on the question.

Typeahead returns in tens of milliseconds with no language model on the keystroke path. Natural-language search sits behind it, grounded in live inventory. Ranking is tuned from an admin screen rather than from code.

  • Instant typeahead across the catalogue
  • Natural-language search grounded in live stock
  • Capability tag taxonomy rather than marketing categories
  • Staff-tunable ranking weights, synonyms, boosts, pinned and buried results, query redirects and facets
  • Zero-result monitoring, keyword analytics and ranking analytics
  • Global search across the admin, configurable per tenant
  • One retrieval service serving both the storefront and the AI layer

Parts, accessories and fitment search is phase two and not yet live.

Analytics and reporting

Cross-business reporting on the operational data, not on an export of it.

  • Cross-business analytics hub
  • Order, product, and pricing comparison analytics
  • Allocation rule analytics and purchase order metrics
  • Goods receipt analytics
  • Customer tier analytics
  • Google Analytics integration alongside first-party data
  • Search, keyword and ranking analytics
  • System health and test status dashboard

Identity and access, axion

Multi-tenant, multi-domain, and validated before your code runs.

  • Complete isolation between tenants
  • Tenant context resolved automatically per domain
  • Google Workspace, Microsoft Entra, Apple ID and email one-time-code sign-in, selectable per tenant
  • JWT sessions with PBKDF2 key derivation at 100,000 iterations
  • Role-based access control down to the individual action, with page-level permissions
  • Token validation at the edge, before application code executes
  • White-label capable

Security, privacy and data protection

Built to the Australian Privacy Principles, and auditable against them.

  • AES-256-GCM envelope encryption on identity and licence fields, and on personal data in object storage
  • Customer contact details masked by default, revealed deliberately, and every reveal logged
  • Customer data access log, reviewable
  • Password-protected and one-time-code protected exports
  • Role and permission enforcement on every endpoint
  • Rate limiting on unauthenticated endpoints
  • Signed webhook verification
  • Runtime input validation on all request data
  • Per-tenant CORS allowlist
  • Privacy request handling for access and erasure
  • OWASP scan status and findings surfaced in the admin

Platform management and configuration

Configuration-driven throughout. Rules, weights and thresholds live in config, not in code.

  • Employee records, registration and staff account management
  • Staff messaging and internal team chat
  • Notification centre, notification settings and popup notifications
  • Business, locality and system settings
  • Per-module settings for POS, OMS, DMS, chat and CMS
  • Menu management and menu design, so navigation is configured rather than deployed
  • Header and holding page configuration
  • Digital receipt, repayment calculator and finance application settings
  • Short link and tag management
  • Bike search and global search configuration
  • Guest customer cleanup

Platform owner and multi-tenancy

One installation, many businesses, operated as a product.

Reserved for the platform operator rather than the tenant.

  • Tenant provisioning and tenant configuration
  • Module matrix and platform feature entitlements, controlling what each tenant sees
  • Supplier portal settings
  • Platform dashboard, monitor and health
  • Cron job management, queue detail and background processing visibility
  • Direct database administration and controlled data clearing
  • R2 object storage management
  • AutoRAG data sync and data sync profiles
  • Google, Honda parts and general integration management
  • Jamtable API settings and integration surface
  • Design system manager, fonts and styling
  • Shop cache configuration
  • Early access lead capture

Migration and onboarding

Getting off the old system without losing the audit trail.

The C9 migration module exists because the founding tenant had twenty years of legacy data. It is a working reconciliation surface, not a one-off script.

  • Migration overview covering datasets, load statistics and reconciliation state
  • Bike reconciliation, identifying stock owned but not visible to a customer
  • Parts reconciliation against the legacy catalogue
  • Load history, so it is clear what was last loaded and when
Planned, not available Marketplace is reserved in the navigation and is not yet built. It is listed here as planned, not available.
Starting point · No theatre

How teams start with Jamtable.

The first step is not a transformation programme. It is a short, practical review of the work already happening: where information lives, where decisions slow down, and which handoffs create avoidable cost. Jamtable runs on Cloudflare Workers, D1 and R2, so there are no servers to patch and no region to be far from.

  1. 01 Map the truth

    Find the messy handoffs first.

    We review the catalogue, customer, order, stock, fulfilment, and partner information that teams already depend on. The goal is to find the repeat questions, duplicated work, and places where people stop trusting the system.

  2. 02 Pick one useful flow

    Start where the pain is visible.

    A first Jamtable workflow might be product questions, fulfilment exceptions, customer follow-up, supplier requests, or internal task routing. Small enough to ship; important enough to prove value.

  3. 03 Connect the working data

    Use the systems you already have.

    Jamtable sits beside the business rather than forcing a rebuild. We connect the useful sources, define the rules, and make the answer layer clear enough for teams and partners to use with confidence.

  4. 04 Prove, then expand

    Measure what gets easier.

    The pilot should reduce a real burden: fewer repeated answers, fewer manual checks, fewer status requests, faster partner responses, or cleaner customer decisions. Once that works, the next workflow is obvious.

15 results Enter to open · Esc to close