Atmora Tech

Customer platform

Commerce that holds up
when the campaign lands

A composable commerce stack: headless storefront API, a catalogue tested to 250,000 SKUs with variant-level pricing, and an order manager that speaks to your ERP rather than replacing it. Built for retailers and manufacturers who have outgrown a hosted cart but do not want to write tax, payment routing and inventory sourcing logic from scratch.

  • Cloud
  • Private cloud
  • Hybrid

Overview

Catalogue, checkout and order management for brands selling to shoppers and to trade buyers on the same stack.

E-commerce Platform runs direct-to-consumer and trade selling from one catalogue and one order book. The storefront is headless, so the web front end, the mobile app and the in-store assisted-selling screen all read the same GraphQL and REST endpoints; pricing, stock and promotion decisions are made server side, once, so the three channels cannot disagree. Underneath sits PostgreSQL for transactional data, an event log for order state changes, and a read model rebuilt from that log for browse and search, which is why a catalogue import does not slow down checkout.

Order state is explicit rather than implied: every order carries a status machine with allowed transitions, and every transition is written with actor, timestamp and reason. That makes reconciliation with the ERP a diff rather than an investigation. It is the wrong choice if you sell under 200 SKUs through a single channel with one payment provider, where a hosted cart will cost a fraction and be live in a fortnight instead of a quarter.

Up 16 percentage points after checkout went from six steps to three at Tinsmith Retail
Checkout completion
New SKU live in about 4 minutes, replacing a nightly batch window
Catalogue publish time
1,800 orders per minute sustained through a 6-hour sale event
Peak order throughput
Up 2.4% from soft-decline retries routed to a second gateway
Payment success rate

Modules

What ships in the box

  • Catalogue and product information management
  • Pricing, price lists and promotions
  • Cart, checkout and payments
  • Order management and fulfilment
  • Search and merchandising
  • Storefront content and campaign pages

Integrates with

  • SAP S/4HANA
  • Microsoft Dynamics 365 Business Central
  • Stripe
  • Razorpay
  • Tally Prime
  • GSTN e-invoicing
  • Algolia
  • Delhivery

Capabilities

What it does

  • Headless storefront API

    GraphQL and REST endpoints for catalogue, cart and orders, with per-channel response shaping. Web, app and store screens read one pricing and stock decision, not three of their own.

  • Variant-aware catalogue

    Products carry attribute sets, media and up to 40 variant axes with per-variant stock and dimensions. Bulk import runs as a background job with a validation report before publishing.

  • Contract pricing for trade buyers

    Customer price lists, volume break tables and negotiated discounts resolve in a fixed order, and checkout shows the buyer which rule produced their price rather than one bare figure.

  • Multi-gateway checkout

    Payment routing across two or more gateways with automatic retry on soft declines, saved instruments, and a reconciliation file per gateway per day matched against captured order totals.

  • Distributed inventory and sourcing

    Stock is tracked per location with soft reservations that expire. Sourcing rules pick the warehouse on distance, stock cover and shipping cost, and can split an order across two sites.

  • Promotions engine

    Cart and line level rules with stacking limits, exclusion groups, budget caps and per-customer usage counts. Every applied promotion is recorded on the order line for later tracing.

  • Returns and refunds

    Return requests carry reason codes, inspection outcomes and restocking decisions. Refunds settle to the original instrument where the gateway allows, and to store credit where it does not.

  • Search and merchandising controls

    Merchandisers pin, boost and bury results per category, set synonym lists and see zero-result queries from the last 30 days. Ranking changes preview against live traffic before publishing.

FAQ

Questions we get asked

Can the ERP stay the master record for stock and pricing?

Yes, and that is the usual arrangement. The platform holds a cached projection with a freshness stamp, applies soft reservations locally so checkout stays fast, and reconciles against the ERP on a schedule you set, typically every 5 to 15 minutes. Where the two disagree, the ERP wins and the difference is logged.

Do trade and consumer selling really share one catalogue?

One catalogue, separate visibility and pricing. A SKU can be published to the trade channel only, carry a minimum order quantity there, and show tax-exclusive pricing to logged-in trade accounts while consumers see the tax-inclusive figure.

How long does a first launch take?

For a single country, one warehouse and one payment gateway, 10 to 14 weeks including catalogue migration. Multi-country tax, several fulfilment sites or a bespoke trade approval flow push that towards 20 weeks. Catalogue data quality, not engineering, is the usual delay.

Start a project

Tell us what is
breaking.

We reply within one working day, and the first call is with an engineer who would actually work on it — not an account manager. If we are not the right studio for the problem, we will say so on that call.

Start a project