Commerce Wiki
A plain reference for the terms that come up in running a commerce business, from SKU to CRDT, with a note on how QuantumOS X3 handles each one today, including where it does not.
Use this as shared vocabulary across engineering, merchandising, finance, and marketing. Where a term has no “In X3” note, it is a general definition only.
How product facts, component selection, compatibility checks and rule administration work together.
Commerce Fundamentals
14 termsSKU
fundamentalsStock Keeping Unit — a unique alphanumeric identifier assigned to a single sellable variant. Every distinct size, color, or configuration gets its own SKU. It is the atomic unit of inventory management and fulfilment.
In X3: A SKU is unique within one business: the product catalog has a unique index on business and SKU together, so two different businesses can use the same SKU without clashing.
Variant
fundamentalsA specific, purchasable form of a configurable product — for example, 'Blue / XL / Cotton'. Variants share a parent product record but each have independent inventory, pricing, images, and weight. A product with three sizes and four colours yields twelve variants.
In X3: A variant is a child product linked to a parent. It has its own SKU and carries its axis values (such as size and colour), and the axes a product can vary on come from its product family.
Bundle
fundamentalsA fixed set of two or more products sold as one line item. Bundles often carry a discount relative to buying constituent items separately. Inventory may be tracked at the bundle level or dynamically deducted from component SKUs at order placement.
In X3: A bundle has its own name and SKU, a price and compare-at price, a percentage or fixed discount, and a list of component products with quantities and an optional variant for each.
Configurable Product
fundamentalsA product that the shopper customises by selecting one or more attribute axes — size, colour, material — before adding to cart. The selection resolves to a specific variant. Configurable products exist as a UI concept; the actual inventory belongs to the resolved variant.
In X3: A configurable product is a parent record whose product family defines the variant axes. Each purchasable combination is a child product (see Variant).
Virtual Product
fundamentalsA product that has no physical form and therefore requires no shipping or inventory tracking — consultations, gift cards, SaaS licences. Payment is captured but no fulfilment workflow is triggered.
In X3: Non-physical items are handled through a digital delivery setting on the product: licence key, download link, voucher code, ticket, policy document, API-provisioned or manual delivery. Each order line gets a delivery record whose status you can follow.
Downloadable Product
fundamentalsA digital asset — PDF, software, audio — sold as a file download. Requires access-controlled, time-limited download links to prevent link sharing. May allow multiple downloads up to a configured limit.
In X3: Delivery records hold a token, an expiry time and an access count, and a delivery can be revoked. In the customer's account, revealing a licence key checks that the delivery belongs to that buyer, has been delivered and has not expired, and counts each access.
Subscription
fundamentalsA recurring purchase agreement where the merchant charges the customer on a defined cadence — weekly, monthly, annually. Subscription commerce requires dunning logic, upgrade/downgrade flows, pause/resume, and cohort-level churn analysis.
In X3: Subscriptions run weekly, biweekly, monthly, quarterly or yearly, with trials, and a scheduled job charges those that are due (Razorpay, Stripe or manual). A failed charge is retried after 15 minutes, 2 hours, 24 hours and 72 hours, and after four failures the subscription becomes past due. There is no proration when a plan changes.
AOV
fundamentalsAverage Order Value — total revenue divided by total number of orders over a period. AOV is a primary lever in growth: lifting it 10% on the same traffic compounds across every channel. Tactics include upsells, cross-sells, free-shipping thresholds, and bundle discounts.
LTV
fundamentalsCustomer Lifetime Value — the projected total revenue a customer generates over their entire relationship with the merchant. LTV drives acquisition spend decisions: a customer expected to spend far more over the years justifies a much higher acquisition cost than one who buys once.
In X3: X3 shows a customer's lifetime value as the sum of their order totals, and you can use it as a field in segment rules. That is spend to date, not a forecast.
CAC
fundamentalsCustomer Acquisition Cost — total marketing and sales spend divided by the number of new customers acquired in a period. Comparing LTV with CAC is the usual unit-economics health check: if lifetime value is not comfortably above acquisition cost, growth may not pay back.
GMV
fundamentalsGross Merchandise Value — the total face value of all orders placed through the platform, before any deductions. GMV is a marketplace or platform-wide metric; it overstates true revenue because it includes seller payouts, refunds, and discounts.
NMV
fundamentalsNet Merchandise Value — GMV after subtracting cancellations, refunds, and fulfilment failures. NMV is the more honest revenue proxy for marketplace operators.
Take Rate
fundamentalsThe percentage of GMV that a marketplace operator retains as revenue — typically covering payment processing, platform fees, and fulfilment services. A take rate of 12% on 1 Cr GMV yields 12 L platform revenue.
In X3: In the marketplace pillar, commission rules apply by category, brand, seller, listing, seller tier or across the whole marketplace, and the rule with the highest priority wins. Each settlement shows the commission, the GST on it, tax collected at source and tax deducted at source.
Commission
fundamentalsA seller-specific or category-specific percentage or flat fee charged against each completed sale. Commissions may be stacked — a base platform commission plus a payment gateway fee, for example.
In X3: Settlements are built from delivered orders only, on a seven-day cycle by default. Marking a settlement as paid is a manual step in the admin with an optional payment reference; there is no built-in payout rail or escrow.
Inventory & Fulfilment
18 termsReservation
inventoryA temporary hold placed on inventory at the moment a customer adds an item to their cart or initiates checkout, preventing another buyer from purchasing the same unit. Reservations must have TTL-based expiry to avoid permanently locking stock that is never purchased.
In X3: At checkout each product is reserved against the best available stock position, using row locks taken in a fixed order so two carts cannot deadlock. The hold lasts 60 minutes, and its status is recorded as held, committed, released or expired. If any product is short, the whole reservation is rolled back and no order or payment attempt is created.
Oversell
inventoryAccepting more orders than available inventory — a failure mode that results in cancellations, disappointed customers, and operational scramble. Oversell typically occurs when inventory checks and order writes are not atomic.
In X3: X3 reserves stock with a single conditional update that only succeeds while available quantity (on hand minus reserved) covers the request, inside one database transaction, so there is no separate check-then-write gap. A database error or shortfall stops the checkout rather than letting it through.
Backorder
inventoryAn order placed against zero or negative inventory, with an explicit expectation that the item will be fulfilled once stock arrives. Backorders require ETA communication, prioritised receiving workflows, and proactive status updates.
In X3: Products carry a backorder policy field, and the admin has a Backorders page that lists backorders by status (pending, partially available, ready or cancelled).
Preorder
inventoryAn order placed before a product is available for sale — typically for upcoming launches. Preorders often require partial or full payment upfront with a promised fulfilment date. They differ from backorders in that no prior stock existed.
In X3: Products carry a preorder flag and a preorder date that can be set in the catalog and in bulk imports.
Wave Picking
inventoryA warehouse fulfilment strategy where orders are grouped into 'waves' — time-based batches — and all picks for that wave are executed simultaneously. Waves are sized to match staff capacity and despatch cut-off times.
In X3: Wave planning scores orders by urgency, using carrier cut-off times and order priority, and splits them into waves of a fixed size, most urgent first. Pickers work a wave on the mobile scanner screen. Zone grouping and walking-path optimisation are not built yet.
Batch Picking
inventoryA method where a single picker collects items for multiple orders simultaneously, visiting each bin location once per walk. Reduces travel time compared to order-by-order picking — effective for high-SKU, low-volume-per-order operations.
In X3: A wave is X3's batching unit. Grouping picks across orders by bin or zone, and optimising the walking path, are not built yet.
Cluster Picking
inventoryA variant of batch picking where the picker uses a cart with labelled compartments — one per order — and sorts items into the correct compartment at the point of pick. Eliminates a separate consolidation sort step.
In X3: Cart-and-tote cluster picking is not a built-in mode. The mobile scanner screens work through a wave.
FEFO
inventoryFirst Expired, First Out — a picking rule that mandates items with the earliest expiry date are picked and despatched first. Critical for food, pharmaceuticals, and cosmetics where selling expired goods creates liability.
In X3: First-expiry-first-out is applied when a store sale uses up ingredient batches through recipes, taking the earliest-expiring batch first. Warehouse picking does not enforce it yet and does not reject a wrong lot automatically.
FIFO
inventoryFirst In, First Out — inventory received earliest is despatched first. The default strategy for non-expiring goods; FIFO prevents old stock from being permanently buried by newer deliveries.
LIFO
inventoryLast In, First Out — most recently received inventory is picked first. Uncommon in physical commerce (creates old-stock risk) but relevant in certain accounting jurisdictions for cost valuation.
Lot Tracking
inventoryAssociating received inventory with a manufacturer lot number, enabling recall traceability. If a lot is recalled, the system can quickly identify all affected units: still in warehouse, in transit, or delivered to customers.
In X3: Lot numbers are recorded when goods are received and travel with picks and stock movements. Lots can be browsed, and an expiring-batch lookup shows stock approaching its expiry date. Each lot number is unique per SKU.
Serial Tracking
inventoryAssigning a unique serial number to every individual unit of a product — used for high-value electronics, medical devices, and warranty-critical items. Serial tracking enables precise unit-level traceability from manufacturer to end customer.
In X3: Serial numbers are recorded against a SKU (unique per SKU) with a status of in stock, reserved, sold, returned or damaged, and can be browsed alongside lots.
Expiry Tracking
inventoryRecording the expiry or best-before date of perishable inventory at the SKU or lot level. Enables FEFO picking, near-expiry alerts, and automatic write-down workflows before stock becomes unsellable.
In X3: Expiry dates are held on lots (batches), and the expiring-batch lookup lists stock approaching its date. Automatic write-down or markdown campaigns are not part of it.
3PL
inventoryThird-Party Logistics — outsourcing warehousing, pick-pack, and shipping to a specialist provider. The merchant retains ownership of inventory but delegates physical operations. Integration requires real-time inventory sync, order push, and tracking number pull-back.
In X3: X3 has carrier connectors that create shipments and labels and fetch tracking with your own carrier accounts. A warehouse run by a third party would need its own integration, so ask us about the specific provider you use.
Dropship
inventoryA model where the merchant takes the order and payment but forwards fulfilment to the supplier, who ships directly to the customer. The merchant never holds stock. Margin is the difference between retail price and supplier cost.
In X3: Dropship routes are rules that match order lines to a supplier, and the highest-priority matching route wins for each line. A dispatch is then sent by email, signed webhook, API or handled manually, and each dispatch can be retried or marked acknowledged.
Ship-from-Store
inventoryFulfilling an online order from a retail store's inventory rather than a dedicated warehouse. Increases inventory utilisation and reduces last-mile delivery distance for nearby customers, often improving delivery speed.
In X3: Order routing rules can send an order to a store, and a pincode lookup picks the location with the best delivery days and available stock. Rules are checked in priority order and the first match wins.
BOPIS
inventoryBuy Online, Pick Up In Store — the customer purchases on the web and collects from a physical location. Requires real-time store inventory visibility, a 'ready for pickup' notification workflow, and a check-in handoff process.
In X3: Shoppers can choose store pickup at checkout, and the store sees the order in a click-and-collect queue in the POS and hands it over.
Endless Aisle
inventoryA retail strategy where store associates can offer customers the full online catalogue — including items not stocked in-store — by placing orders on a tablet or POS terminal for home delivery or store pickup. Eliminates lost sales from local stockouts.
In X3: Store staff can place an order from a store's own screen for stock that is held elsewhere.
Orders & Payments
11 termsOrder Lifecycle
ordersThe sequence of states an order transitions through from placement to completion — for example pending (captured, not yet confirmed), confirmed, shipped, delivered, and then returned or refunded. Each state change can trigger downstream actions.
In X3: Orders move through a defined set of states: draft, pending, confirmed, on hold, processing, packed, shipped, in transit, out for delivery, delivered, delivery attempted, return to origin, returned to warehouse, cancelled, returned and refunded. The allowed moves are enforced in application code, so for example a pending order cannot jump straight to shipped, and shipping requires a tracking number.
Payment Capture vs Authorisation
ordersAuthorisation places a hold on the customer's funds without moving money. Capture is the subsequent step that actually moves the funds to the merchant. Many merchants authorise at order placement and capture only when the order ships, reducing disputes on cancelled orders.
In X3: The Razorpay connector relies on Razorpay's default automatic capture, so a successful payment is captured straight away, and refunds are supported. Holding a payment and capturing it when the order ships is not offered.
Settlement
ordersThe final transfer of funds from the payment gateway's holding pool to the merchant's bank account. Settlement timing varies by gateway: same-day, T+1, or T+2. Marketplace platforms must split settlements between the platform and multiple sellers.
In X3: For marketplace sellers, a settlement is built from delivered orders and shows commission, GST on commission, tax collected at source, tax deducted at source and any reserve held back. The default cycle is seven days, and paying the seller is recorded by hand.
Chargeback
ordersA payment reversal initiated by the cardholder's bank, typically following a dispute. Chargebacks carry fees and damage merchant health scores with payment networks. Merchants have a limited window to submit evidence contesting fraudulent chargebacks.
In X3: Finance has a chargeback case log: your team records a case against a transaction with the amount, reason code and evidence, and moves it through open, disputed, won or lost. Cases are entered by your team and are not created automatically from gateway notices.
Fraud Signals
ordersData points used to assess whether an order is likely fraudulent: velocity (too many orders from one IP), address mismatch, device fingerprint, BIN country vs billing country, and behavioural anomalies. High-risk orders may be auto-cancelled or routed for manual review.
In X3: After an order is created, the active fraud rules that match it add up their weights: under 30 is allowed, 30 to 60 goes to review, 60 to 90 is held and above 90 is blocked. Rule types are order velocity, order amount, account age, email patterns, country mismatch and blocked payment methods. Held and blocked orders go on hold with the reason, and the score and rules that fired are saved with the order.
COD
ordersCash on Delivery — payment is collected by the courier at the moment of delivery. Common in markets where card use is lower. COD orders carry higher return rates and operational cost but enable broader market reach.
In X3: Checkout rules can allow or deny COD using conditions such as pincode, state, country, order value, the customer's risk band and past COD history, and can require a part-payment in advance. Finance can import a courier's remittance file and match it against COD orders to see which have not been remitted or differ in amount.
NET Terms
ordersA payment arrangement common in B2B commerce where the buyer pays within a defined number of days after invoice — NET 30 means payment is due 30 days after the invoice date. Requires credit risk assessment and dunning workflows for late payments.
In X3: You assign NET payment terms and a credit limit to each business account. Each invoice keeps the terms that applied when it was issued, and buyers see invoices as paid or outstanding.
PO Checkout
ordersA checkout flow where the buyer submits a Purchase Order number rather than paying immediately. The seller fulfils against the PO and invoices later. Standard in public sector and large enterprise procurement workflows.
In X3: In the B2B portal, buyers send purchase orders that are checked against the account's rules before they reach your team. The buyer's PO reference and document stay with the request.
Quote
ordersA formal price proposal presented to a buyer before they commit to purchasing. Quotes may include custom pricing, volume discounts, or special terms. A quote-to-order flow converts an accepted quote into a confirmed order without re-entering line items.
In X3: In the B2B portal a buyer requests a quote for several products, your team reviews price, stock and lead time before issuing it, and the buyer follows it from draft to accepted, rejected or expired. Revisions are recorded, and expired quotes can be renewed.
RMA
ordersReturn Merchandise Authorisation — a formal approval allowing a customer to return a product. RMAs include a reference number, return window, condition requirements, and instructions for the courier label. They prevent unauthorised or fraudulent returns.
In X3: Customers request a return from their order and say whether they want a refund, a replacement or store credit. Your team then inspects each returned item and records the decision, condition notes and photos, with accepted and rejected quantities.
Return Authorisation
ordersSynonymous with RMA — the explicit approval that a return is accepted. Distinct from refund, which is the financial step that may follow a return. Returns may be inspected before a refund decision is made.
In X3: Accepting a return puts the accepted items back into stock at a restock location you choose and reverses the loyalty points earned on that order. Store credit goes to a wallet with an append-only ledger. There is no guided grading workflow for returned items yet.
Customer & Loyalty
14 termsCustomer 360
customerA unified view of a customer aggregating data from every touchpoint: browsing history, purchase history, support tickets, loyalty status, email engagement, and in-store visits. The 360 view enables personalised experiences and informed agent interactions.
In X3: The customer timeline in the admin merges events from sales, marketing, operations, loyalty and service into one list. Each source is loaded separately with its own time limit, so one slow or failing source is reported as unavailable instead of blanking the whole view.
LTV Bands
customerSegmentation of the customer base into groups by Lifetime Value — for example, the top 5% by LTV vs the bottom 50%. LTV bands inform acquisition spend, retention priority, support SLAs, and personalised reward structures.
In X3: You can build LTV bands as segments: a rule on lifetime value (greater or less than a figure you choose) groups customers, and the segment can then drive journeys and campaigns.
Cohort
customerA group of customers who share a common acquisition attribute — typically the month they made their first purchase. Cohort analysis tracks how different acquisition cohorts retain, spend, and churn over time.
Segment
customerA dynamic or static group of customers matching a defined set of criteria — 'customers in Chennai who purchased in the last 30 days with an AOV above 2,000'. Segments power targeted campaigns, pricing rules, and loyalty experiences.
In X3: A segment is a set of rules joined by AND and OR, with groups nested inside groups. Fields include email, name, phone, city, country, sign-up date, order count, lifetime value, last order date, loyalty points and loyalty tier. The segment is worked out against your live customer and order data when you ask for it, with a count and sample preview before you save. Browsing sessions, returns and support tickets are not available as fields yet.
CDP
customerCustomer Data Platform — a system that collects, unifies, and activates customer data across channels. A CDP stitches together anonymous and identified profiles and makes unified data available to downstream tools like email, ads, and personalisation.
In X3: X3 is not a separate CDP. Customers, orders and loyalty share one customer record, and segments are built from that live data with no copy in a separate analytics store.
RFM Analysis
customerRecency-Frequency-Monetary scoring — ranking customers on three axes: how recently they purchased, how often they purchase, and how much they spend. RFM produces a score like '5,5,5' (best customer) that powers segmentation without predictive modelling.
In X3: A customer scoring run, started from the Intelligence area of the admin, gives each customer a frequency score and a spend score from fixed order-count and revenue thresholds, adds days since the last order, and labels them champion, loyal, at risk, hibernating or new. The thresholds are built in and are not tuned per business.
Tier
customerA named loyalty level that a customer achieves by meeting a spend or points threshold — Bronze, Silver, Gold, Platinum. Tiers typically carry escalating benefits: higher earn rates, free shipping, priority support.
In X3: Each tier has a lifetime-points threshold you set. When points are granted, X3 finds the highest tier the customer's lifetime points reach and moves them up, recording a tier-unlocked event. The purchase earn rule can apply a different points multiplier for each tier.
Points
customerA loyalty currency earned on purchases and redeemable for discounts or rewards. Points are a proven retention mechanism but require careful design of earn rate, redemption rate, and expiry policy to avoid liability runaway.
In X3: Every earn, redemption and reversal is written as its own ledger row, and the customer's balance and lifetime points are updated in the same database step. A return reverses the points earned on that order. Points can carry an expiry date, and a liability view shows what you owe in points.
Cashback
customerA loyalty variant where a percentage of spend is returned to the customer as real monetary credit applicable to future purchases. Cashback feels more tangible than points and has higher perceived value, but creates a direct P&L liability.
In X3: Cashback has its own wallet and its own ledger, separate from the points ledger.
Earn Event
customerAn action that grants loyalty points or cashback — a purchase, a product review, a referral, a birthday, a social share. Earn events are defined per tenant with configurable multipliers.
In X3: A purchase rule sets how many points a customer earns per 100 of order value, multiplied by their tier and by any active bonus campaign. Rules also cover reviews, sign-ups, referrals, shares, birthdays and streaks.
Burn Event
customerThe redemption of loyalty currency — applying points or cashback against an order total. Burn events reduce the loyalty liability and must be consistent even if the order is subsequently cancelled or refunded.
In X3: A redemption writes a negative ledger entry and a redemption record. When a return is accepted, X3 reverses the points earned on that order. Restoring points that a customer spent on a cancelled or refunded order is not automatic.
Dunning
customerThe process of communicating with customers about failed or overdue payments — subscription renewals, invoice settlements, instalment plans. Effective dunning sequences retry payments on a smart schedule and graduate from soft to firm messaging.
In X3: A failed subscription charge is retried after 15 minutes, 2 hours, 24 hours and 72 hours, and after four failures the subscription is marked past due and an event is raised. Finance can also keep dunning campaigns with steps by email, SMS or call and record each send.
Churn Prediction
customerUsing historical purchase patterns to forecast which customers are likely to stop buying. A customer who previously ordered monthly but has not ordered in 60 days is a churn candidate. Early identification allows intervention before the customer is lost.
In X3: The customer scoring run estimates churn risk from the days since the customer's last order. It is a simple rule, not a trained model, so use it to find lapsed customers rather than to forecast individuals.
Win-back
customerA campaign targeting lapsed customers who have not purchased in a defined window. Win-back messaging typically includes an incentive — discount, free shipping, or a personalised offer — to re-engage.
In X3: The marketing agent can recommend a campaign or journey for lapsed customers, and you approve, edit or schedule it. Journeys send through the SMS, WhatsApp and email providers you have connected.
Marketing & Growth
12 termsFunnel
marketingThe sequential stages a prospective customer moves through from first awareness to purchase — Awareness, Interest, Consideration, Intent, Purchase, Retention. Each stage has an associated conversion rate; the product of all stage rates is the end-to-end funnel conversion.
Conversion Rate
marketingThe percentage of visitors who complete a desired action — adding to cart, initiating checkout, placing an order. Measured at each funnel stage. For example, lifting checkout conversion from 60% to 65% adds about 8.3% more orders on the same traffic.
Cart Abandonment
marketingWhen a customer adds items to their cart but leaves without completing checkout. Recovery messages sent soon after abandonment can win back some of that revenue.
In X3: A recovery service detects abandoned carts and started checkouts and contacts the customer in steps. For carts the default cadence is an email after 1 hour, an SMS after 20 hours and a WhatsApp message after 48 hours, using whichever contact details exist. Failed payments and stalled quotes have their own cadences.
Journey Automation
marketingA series of timed, conditional marketing touchpoints triggered by customer behaviour or lifecycle events. Journeys replace one-size-fits-all blasts with personalised sequences: new customer onboarding, post-purchase follow-up, re-engagement.
In X3: Journeys are built on a canvas from trigger, condition, action, wait and end nodes, with A/B splits in conditions. Actions send SMS, WhatsApp or email through your own providers, or move the customer to a new stage. Tag, segment and discount steps are only recorded as run for now. Journeys are processed on a 10-minute cycle, so a message goes out within about that window rather than instantly, and there is no dry-run mode.
Triggered Campaign
marketingA message or sequence that fires automatically in response to a specific customer action or event — browse abandonment, low loyalty balance, a birthday, or a product review. Triggered campaigns usually perform better than batch sends because they arrive when the customer is already engaged.
In X3: Journeys start from a trigger node. Separately, the marketing agent raises recommendations on triggers such as ageing inventory, lapsed customers, abandoned carts, festivals, new-customer welcomes, replenishment and weekend flash sales.
A/B Test
marketingA controlled experiment where two or more variants of a page, message, or price are shown to randomly assigned user groups. Statistical significance is reached when the observed difference is unlikely to be due to chance.
In X3: Theme tests split visitors between two themes, assign each visitor deterministically so they keep the same theme, and compare add-to-cart, checkout and purchase goals with a significance test. Page-builder tests record conversion revenue and report the probability that a variant beats the baseline. One theme experiment runs at a time for a business.
Holdout Group
marketingA control group deliberately excluded from a campaign or experiment to provide a clean baseline. Holdouts measure the true incremental lift of a campaign — what would have happened without any intervention.
In X3: A holdout group for reactivation campaigns is planned, not live. Until it is, use an A/B split in a journey condition to compare against a group that does not receive the message.
Attribution
marketingThe process of assigning credit to marketing touchpoints that preceded a conversion. Models include last-click (simple), first-click (awareness-focused), linear (equal credit), time-decay (recency-weighted), and data-driven (ML-based).
In X3: X3 credits orders to marketing touches with five rule-based models: first touch, last touch, linear, time decay and position based. They are for comparing channels, not for proving what caused a sale, and there is no data-driven or incrementality model.
ROAS
marketingReturn on Ad Spend — revenue generated per unit of ad spend. A ROAS of 4x means every rupee spent returns 4 in revenue. ROAS is the primary efficiency metric for performance marketing teams.
In X3: When ad sync is enabled, X3 reads Google and Meta campaign data, including spend and conversion value, and stores ROAS for each campaign and day. TikTok and Pinterest spend are not imported.
CPM
marketingCost per Mille — the cost to serve 1,000 ad impressions. A CPM pricing model is used for awareness campaigns where brand exposure is the goal rather than immediate conversion.
In X3: For connected Google and Meta accounts, X3 stores impressions, spend and CPM for each campaign and day.
CPC
marketingCost per Click — the cost of each click generated by an ad. CPC is used in search and social advertising where the advertiser pays only when a user clicks through.
In X3: For connected Google and Meta accounts, X3 stores clicks, spend and CPC for each campaign and day.
CPA
marketingCost per Acquisition — the total ad spend divided by the number of conversions (orders, sign-ups, etc.). CPA is a direct measure of performance-channel efficiency and is the natural complement to CAC.
Platform & Technical
13 termsISR
platformIncremental Static Regeneration — a Next.js rendering strategy that pre-renders pages at build time and re-generates them in the background on demand without taking the page offline. ISR combines the performance of static HTML with the freshness of server rendering.
In X3: The storefront sends cache headers that let the edge serve a stored page while it is refreshed in the background, and keep serving it if the origin errors. Pages are tagged, so a change purges only the pages it affects, and the admin has a manual purge.
Edge Function
platformA serverless function deployed to a CDN edge network and executed close to the end user. Edge functions are ideal for personalisation, A/B routing, authentication checks, and geo-based redirects.
In X3: The storefront is a Next.js application built for Cloudflare Workers with OpenNext. One deployment can serve many businesses, each with its own domain, theme and data, and a business that needs it can have a dedicated Worker.
CDN
platformContent Delivery Network — a globally distributed network of servers that cache and serve static assets (images, CSS, JS) from locations close to the user, reducing time-to-first-byte.
In X3: The storefront is served through Cloudflare. Requests for the same uncached page at the same moment are merged into one request to the origin. In a scripted check on 5 July 2026, The Value Store's cached home, shop and category pages answered at a median of 67 to 77 ms and a 95th percentile of 112 to 151 ms from one test location; that is one business measured from one place, not a guarantee for every shop.
Webhook
platformAn HTTP callback that one system sends to another when an event occurs — an order is placed, a shipment is despatched, a payment fails. Webhooks enable real-time integrations without polling.
In X3: Webhook deliveries are signed with HMAC-SHA256, and every attempt is logged with its status and response. A delivery is tried three times with a growing delay, and one that still fails goes to a dead-letter list that is retried after ten minutes. You can send a test event from the admin. There is no one-click replay of old events yet.
Idempotency
platformThe property of an operation that can be applied multiple times without changing the result beyond the first application. Critical in payments and order APIs — a network retry should not result in a duplicate charge.
In X3: Selected admin write procedures accept an Idempotency-Key. Within 24 hours, a repeat with the same key and the same body returns the first result, and the same key with a different body is rejected. The key is optional: a request without one is not protected.
Event Sourcing
platformAn architectural pattern where state changes are stored as an immutable, append-only sequence of events rather than as mutable row updates. The current state is derived by replaying events. Provides a full audit trail and enables temporal queries.
In X3: X3 is not event-sourced. Orders are rows whose status changes in place, stock reservations are rows with a status, and points are an insert-only ledger next to a stored balance. Some changes also raise events, and the partner bridge writes events to an outbox in the same transaction as the change.
CQRS
platformCommand Query Responsibility Segregation — separating the write model (commands that change state) from the read model (queries that return data). Allows each side to be optimised independently: writes for consistency, reads for speed.
In X3: X3 does not apply CQRS across the platform. The nearest example is product search, which reads from a flattened search table that the database keeps current whenever a product is saved.
Saga Pattern
platformA distributed transaction pattern where a multi-step operation — place order, reserve inventory, charge payment, create shipment — is managed as a sequence of local transactions, each with a compensating action on failure. Avoids distributed locks across services.
In X3: Checkout is not run as a saga. Stock for the whole cart is reserved in one database transaction that rolls back completely on a shortfall, and reserved stock is released on payment-failure and cancel paths. A payment that was captured but cannot be fulfilled is flagged for reconciliation.
CRDT
platformConflict-free Replicated Data Type — a data structure that can be updated concurrently on multiple nodes and merged without conflicts. CRDTs are foundational for offline-first applications where local state must sync after reconnecting.
In X3: The POS does not use CRDTs. Completed sales are queued in the browser's storage and sent when the connection returns, checked every 30 seconds, and each sale has a local id so a duplicate is stored once. Offline limits for a terminal can be set but are not enforced yet, and the register keeps no local copy of the catalog, so keep the page open while offline.
RLS
platformRow-Level Security — a Postgres feature that enforces data access policies at the database layer by filtering rows based on the executing user's context. RLS provides a structural guarantee of tenant isolation even if application-layer bugs bypass normal query scoping.
In X3: The admin sets the business id on each database session, and many tables carry a tenant-isolation policy that checks it. Enforcing those policies is a deployment setting (ENABLE_TENANT_RLS) that is off by default. When it is off, the application's own business scoping is the only enforcement, so treat RLS as an optional second safeguard rather than a guarantee.
OAuth Scopes
platformFine-grained permissions declared during an OAuth flow that limit what an authorised application can access. A 'read:orders' scope grants order read access without write access or customer data access.
In X3: The public REST API under /api/v1 limits every request by scopes such as products:read, orders:write or inventory:write. Apps connect with OAuth 2.0 (authorisation code with PKCE, refresh tokens or client credentials), or with API keys. Access tokens last one hour and refresh tokens 30 days.
tRPC
platformA TypeScript-first RPC framework that generates end-to-end type-safe API contracts without a schema file or code generation step. The client infers types directly from server procedure definitions, making breaking changes a compile-time error.
In X3: The admin is built on tRPC with Zod input validation. The public API is separate: hand-written REST with a hand-maintained OpenAPI document, not generated from tRPC.
pgvector
platformA Postgres extension that adds vector similarity search — cosine, L2, and inner product — to standard Postgres tables. Enables semantic search, product recommendations, and embedding-based retrieval without a separate vector database.
In X3: The admin keeps embeddings in Postgres with pgvector for its knowledge-base retrieval, using a cosine index. Storefront meaning-based search is different: it uses Cloudflare Workers AI embeddings matched against a Vectorize index kept for each business, and falls back to keyword results if that lookup is slow or down.
International Commerce
12 termsMarket
internationalA configured selling destination defined by a combination of country, currency, language, tax region, and shipping rules. A merchant selling to India, UAE, and UK is operating three markets, each with distinct pricing, tax, and content requirements.
In X3: The storefront has country profiles for India, the UAE, Singapore, the UK, Malaysia and Bangladesh. Each carries its currency, default language, address format, delivery partners and payment methods.
Locale
internationalA combination of language and region code — en-IN, ta-IN, ar-AE — that drives storefront language, date formatting, number formatting, and right-to-left text rendering.
In X3: The storefront interface supports a long list of languages, including right-to-left scripts such as Arabic. Product names and descriptions can be stored in nine Indian languages (Hindi, Tamil, Telugu, Bengali, Kannada, Malayalam, Marathi, Gujarati and Urdu) and fall back to English when a translation is missing.
Currency
internationalThe monetary unit in which prices are displayed and charged. Multi-currency storefronts must handle display currency (for the shopper) vs settlement currency (for the merchant's bank) and FX conversion between them.
In X3: Shoppers can switch the display currency, and prices are converted with cached exchange rates (see FX Rate).
FX Rate
internationalThe exchange rate between two currencies at a given time. FX rates fluctuate continuously; merchants must decide whether to lock in rates (predictable margins, FX risk for merchant) or float them (accurate pricing, potential shopper confusion from price changes).
In X3: Storefront rates come from a public rate feed that is fetched on the server and cached for six hours, with a stored set of rates used if the feed is unavailable. In the admin, a looked-up rate is cached for 24 hours.
CLDR
internationalCommon Locale Data Repository — the Unicode consortium's authoritative data set for locale-specific formatting rules: number separators, date patterns, plural forms, measurement units, and calendar systems.
In X3: Prices are formatted with the standard Intl number formatter for each currency's locale, which uses CLDR data from the runtime. If that fails, a plain symbol and amount are shown.
hreflang
internationalAn HTML attribute that tells search engines which version of a page is intended for which language and region. Proper hreflang implementation prevents duplicate content penalties and ensures the correct locale ranks in each market's search results.
Tax Region
internationalA geographic jurisdiction with its own tax rules — rates, exemptions, and filing requirements. Tax regions may be country-level (India GST), state-level (US sales tax), or category-level (UK zero-rated food).
In X3: Checkout tax is built for Indian GST. The rate comes from the product's compliance record, and the buyer's state is compared with the seller's to decide the split. The breakup is stored on the order.
VAT
internationalValue Added Tax — a consumption tax applied at each stage of the supply chain, with businesses reclaiming VAT on their purchases. The end consumer bears the full VAT cost. Dominant in Europe, India (as GST), and the Middle East.
In X3: A storefront setting controls whether displayed prices include tax and what the tax is called (GST by default). Checkout tax calculation is GST for India; X3 does not claim a general VAT engine for other countries.
GST
internationalGoods and Services Tax — India's unified indirect tax replacing the prior VAT/service tax patchwork. GST uses a small set of rate slabs, product-level HSN code classification, and periodic return filings. Rates and rules change, so check the current schedule.
In X3: At checkout GST is worked out per line from the product's HSN-based rate: CGST plus SGST when the buyer's state matches the seller's, and IGST otherwise. Business buyers get GST tax invoices, and the Books module can generate a GSTR-1 or GSTR-3B period summary of taxable value, IGST, CGST and SGST. X3 does not file returns on the GST portal.
HSN Code
internationalHarmonised System of Nomenclature code — an internationally standardised product classification code used in India's GST system to determine the applicable tax rate. 6-digit codes cover broad categories; 8-digit codes are more specific.
In X3: Products carry an HSN code and GST rate, and the POS applies per-location tax rates by HSN code. An AI step in the catalog tools can suggest HSN codes and GST rates; check its suggestions before relying on them.
Customs HS Code
internationalThe Harmonised System code used in international trade customs declarations. Required on commercial invoices for cross-border shipments to determine import duties and eligibility for trade agreement preferences.
DDP vs DDU
internationalDelivered Duty Paid (DDP) means the seller pays all import duties and taxes — the buyer receives the package with no surprise charges. Delivered Duty Unpaid (DDU) means the buyer is responsible for clearing customs and paying import duties.
B2B Commerce
8 termsBuyer Group
b2bA named classification applied to B2B buyer accounts that controls which catalogues, price lists, and payment terms they can access. A hospital buyer group might see medical supply pricing; a retail buyer group sees standard wholesale pricing.
Price List
b2bA defined set of prices applied to a specific customer segment, buyer group, or geographic market — potentially overriding the base catalogue price. A single product may have dozens of active price lists simultaneously.
In X3: In the B2B portal you set prices for a single business account, with start and end dates and unit prices that step down by quantity. At the POS, price lists with rules can be applied.
PO
b2bPurchase Order — a formal document issued by a buyer authorising a supplier to deliver goods or services at a specified price. POs define quantity, unit price, delivery terms, and payment terms. They create a binding commercial obligation.
In X3: Buyers send purchase orders from the portal, and each is checked against the account's rules before it reaches your team. Buyers can ask to change or cancel an order until it is locked for fulfilment.
Quote-to-Order
b2bThe workflow converting a sales quote into a confirmed purchase order. Once a buyer accepts a quote, the agreed pricing, quantities, and terms are locked in and a binding order is created without re-entering data.
In X3: Accepting a quote in the portal starts the order, so the buyer does not re-enter the lines.
Credit Limit
b2bThe maximum outstanding balance a buyer can carry before further orders require prepayment. Credit limits are typically set by the seller's finance team based on payment history and creditworthiness.
In X3: Each business account has a credit limit, and orders that would go over it can be flagged or blocked. Buyers see their available credit on the dashboard and can request a credit review.
Approval Workflow
b2bA structured review process where orders above a threshold — by value, by product type, or by customer — require explicit sign-off from a designated approver before proceeding. Common in enterprise procurement to enforce spend controls.
In X3: A requester at the customer raises a purchase request tagged to a cost centre, and it goes to an approver. Order-value limits send larger purchases to the right level, an approver who is away can delegate for a set period, and a record shows who approved each purchase.
Company Account
b2bA B2B entity representing an organisation rather than an individual — with a business name, tax ID, credit terms, and multiple authorised buyer contacts underneath it. Company accounts separate personal and business identity.
In X3: You approve each business before it can see any prices or orders. The account keeps billing, shipping and branch addresses, and its GSTIN and PAN.
Buyer Contact
b2bAn individual user who belongs to a B2B company account and can place orders on behalf of that company. Buyer contacts may have role-based permissions — some can place orders, others can only view invoices.
In X3: Several people at one customer share an account with owner, requester, approver and finance roles.
The capabilities built into the platform, each checked against the product as it runs today, with limits stated.
Read more →Storefront, POS, orders and warehouse, marketplace, loyalty, platform, AI, conversational commerce, migration and B2B, with what is live and what is not.
Explore features →Search, fraud screening, segments, the marketing agent and the admin copilot, and how you control them with your own keys and rules.
Learn about Kynetra →QuantumOS Dispatch
Insights for commerce operators
Operator stories, platform deep dives and notes on what ships.
We'll send the QuantumOS Dispatch by email. Unsubscribe any time. See our privacy notice.
Want to see how these concepts work on your own catalog and orders?