Xirag Register for early access

Xirag for Ecommerce

Xirag ecommerce for the whole store

For online stores and marketplaces: catalogue, checkout, orders, returns, cash on delivery, offers, fulfilment and seller settlement on the same core as every Xirag module, with named seats, maker-checker approvals and an audit trail you can prove.

Register for early access See the capabilities

Ecommerce modules are planned; payments run on Xirag Payments. Every workflow works for people on their own. Agents are not offered at launch; they are provided on request later.

Xirag for Ecommerce · Order journeyDemo
  1. Discover
  2. Cart
  3. Payment
  4. Fulfil
  5. Deliver
  6. Settle
  • CheckoutOrder from Kavya (demo) paid by UPI on a second gateway after the first declined
  • FulfilShipment booked, waybill attached to the order
  • ReturnsReturn inspected at the warehouse, refund request raised
  • CheckerRefund above the desk's limit approved by the finance controller
Illustrative mock-up with fictional demo data; most steps are planned ecommerce modules, not a live console.
Capabilities

Ecommerce ERP for everything behind the buy button

From the first product page to the seller's settlement, each area builds on Xirag modules that already share people, departments, approvals and the audit trail.

  • Storefront

    Themes, pages, navigation and merchandising on your own site, with conversion tracking built in.

    Planned · builds on Website Builder

  • Catalogue and pricing

    Products, variants, collections and availability, with a second approver for price changes.

    Planned · builds on the audit trail

  • Checkout

    One-click checkout, saved methods, a retry screen after a failure and recovery of abandoned carts.

    Planned · builds on Xirag Payments

  • Orders

    Every order with its attempts, notes, shipment and conversation on one record.

    Planned · builds on Payments, CRM

  • Returns and refunds

    Return authorisation, pickup and inspection, then a refund request tied to the original payment.

    Planned · builds on Payments

  • Cash on delivery

    COD rules per order, partial COD, conversion to prepaid, and return-to-origin tracking.

    Planned · builds on Payments

  • Offers and coupons

    Coupons, promotion codes and payment offers with budgets, limits, best-offer selection and rollback.

    Planned · builds on Payments

  • Inventory

    Stock by location, reservations at checkout and replenishment alerts, or a link to the system you use.

    Planned · builds on the shared core

  • Fulfilment and shipping

    Pick, pack, shipment booking and delivery handoff, with shipping profiles per zone.

    Planned · builds on Xirag for Logistics

  • Marketplace

    Seller onboarding, signed seller agreements, commissions and split settlement to each seller.

    Planned · builds on Payments, CLM, eSign

  • Growth

    SEO, campaigns and social selling, with marketing consent recorded per shopper.

    Planned · builds on Website Builder, CRM

  • Analytics and service

    Funnel, return and COD reports, and shopper tickets linked to the order they are about.

    Planned · builds on CRM, Messenger

Beyond a commerce platform

What one agentic core changes

A store platform takes orders. Xirag also keeps who is responsible for each one, who approved every refund, and a record of the money nobody can quietly rewrite.

  • Seats outlive the sale season

    "Returns desk" and "Seller settlements" are seats. When someone leaves after the festive rush, their open refunds stay with the seat.

  • A checkout that routes around outages

    Payments are routed by rules and success rates, and a declined attempt can retry on the next gateway, so one outage does not stop the store.

  • Returns that carry their money

    An inspected return becomes a refund request on the original payment, and a refund above the desk's limit needs the finance controller.

  • Seller splits with a second approver

    Changing a seller's share or settlement account needs a checker, and every split is recorded; a licensed partner moves the money.

  • COD that reconciles

    Delivered COD orders are matched to the carrier's remittance, so missing cash shows up as a break to work, not a month-end surprise.

  • Offers with a budget and an undo

    Payment offers carry a budget and limits, the best one applies at checkout, and a mistaken offer can be rolled back.

  • Prices nobody edits quietly

    Price, refund and payment changes go to an audit trail where each entry is linked by hash to the one before, so an edit shows.

  • Agents that draft, people who decide

    On request, agents can draft catalogue copy, flag risky COD orders and prepare return decisions, and a person approves each. Agents are not offered at launch; they are provided on request later.

Payments powered by Xirag Payments

The store's money on a real payments stack

Checkout, refunds and seller settlement run on Xirag Payments, the stack Xirag provides to payment aggregators and gateways, with versioned APIs and signed webhooks for the store systems you connect. Xirag Payments is in development and runs in a sandbox; money movement is partner-backed.

Explore Xirag Payments
  • One-click checkoutWith a retry screen after a failure
  • Routing and failoverAcross your gateway connections
  • Cash on delivery rulesPer order, partial COD, prepaid conversion
  • Payment offers and EMIWith budgets, limits and rollback
  • Refunds tied to returnsFull and partial, with a checker above limit
  • Marketplace split settlementPer seller, partner-backed
  • Store plugins and syncWith a store reconciliation report
  • Subscriptions and mandatesFor repeat orders
Trust for shopper data

Built to protect the people who buy from you

Shopper addresses, payments and order history deserve more than a password. These are the principles the product is designed around.

  • Audit trail

    Every change to an order, a price or a refund is written with who, when, before and after, linked by hash to the entry before it.

  • Maker-checker

    Large refunds, seller split changes and turning off a payment method need two people: one asks, another approves.

  • Consent first

    Marketing consent is recorded per shopper and purpose before a campaign uses it, and every consent is on the audit trail.

  • Role scopes

    People see what their role and department allow. An agent, when a client asks for one, acts only within the scopes of its seat.

These are design principles of the product, not certifications.

Early access

Shape Xirag for your store

Register for early access, or tell us how your store or marketplace runs checkout, returns, COD and seller payouts today.

Register for early access Talk to us