E-commerce for retail chains
A storefront under your own domain on the same catalogue and stock as the tills, orders fulfilled from the outlets and the warehouse, and every settlement and e-invoice in one place. Bought once and owned outright.
- Your own domain
- The storefront, the customers and the orders are yours.
- One catalogue
- The store, the marketplaces and the tills read one record.
- Nearest stock
- Orders go to the site that can ship soonest.
- Owned outright
- No percentage of sales.
From the product record to the parcel at the door
Six parts of one platform, for head office, operations, finance and the platform team.
- The storefrontYour domain, your brand, and stock at the nearest outlet.
- Catalogue and pricesOne record for the store, the marketplaces and the tills.
- MarketplacesListings out, orders back into the same queue.
- Orders and fulfilmentOne queue, allocated to the site that can ship soonest.
- Stock and purchasingStock by site, replenishment and purchase orders.
- Settlement and e-invoicingPayouts matched to orders, and e-invoices on request.
A day of orders on asasii commerce
From the campaign going live in the morning to the payouts matched the next day.
The campaign goes live
In store and online on the same date, with overlaps checked before it started.
An order is placed
On the storefront, paid by FPX, card or wallet.
Allocated to the nearest stock
The outlet or warehouse that can ship soonest takes the order.
The picking wave
Picked, packed and labelled for the carrier.
A collection is ready
Reserved against the outlet's stock and waiting with the promised hour.
Carrier handover
Parcels go with their labels, and the customer's account shows them on the way.
Collected at the counter
The customer shows a code and the order closes on collection.
Payouts matched
Gateway and marketplace payouts matched to orders and fees, with days late flagged.
Who it's for
Each team works on its own screen, on the same orders.
A licence, not a storefront that belongs to someone else
The retailer buys a system and keeps everything it produces. idataraya is paid to build, customise and maintain it.
| Topic | A hosted commerce platform | asasii commerce |
|---|---|---|
| Who owns the software | The platform; access ends with the subscription | The retailer, outright |
| The storefront | On the platform's domain and terms | Under the retailer's own domain and brand |
| Customer data | Held by the platform | Held by the retailer, exported on request |
| The tills | A separate system, synced by a connector | asasii pos on the same catalogue and stock |
| What it costs | A subscription plus a percentage of sales | A system, plus a yearly fee with defined response times |
Security and Malaysian compliance
The questions a retail group's audit committee asks, answered in the platform.
Security and data overview- MyInvois e-invoicing
- Orders as e-invoices on request, consolidated B2C on schedule.
- PDPA 2010
- Customer accounts, orders and addresses stay with the retailer.
- PCI DSS
- Card data stays with the gateway. The platform holds tokens only.
- Single sign-on and MFA
- On every console, with roles scoped by outlet and function.
- Your own domain
- The storefront runs under the retailer's own domain and certificate.
- Audit trail
- Every action recorded with the previous value and kept for seven years.
Rolled out and maintained by idataraya
asasii commerce runs in the retailer's own cloud account or data centre. idataraya installs it, connects the channels and keeps it current, and the retailer holds the keys, the backups and the data.
- Each gateway, marketplace and carrier connected once
- The storefront's uptime reported monthly
- Storefront updates under the yearly agreement
- Response times by severity, measured monthly
Questions retailers ask
About the storefront, the channels, orders and the agreement.
Does the storefront run on our domain?
Yes. The store runs under the retailer's own domain and brand, with the retailer's certificate. Customers register with the retailer, and their accounts, orders and addresses are the retailer's data.
Which marketplaces and gateways does it connect to?
Listings, prices and stock are pushed to the marketplaces the retailer sells on and orders pulled back into the same fulfilment queue. FPX, cards and e-wallets are taken through the retailer's own gateway. Each connection is set up once for the retailer.
How does click and collect work?
The customer chooses an outlet at checkout, the order is reserved against that outlet's stock, and the outlet sees it waiting with the promised hour. The customer shows a code at the counter, and the order closes on collection.
Does it handle MyInvois?
Yes. Orders can be issued as validated e-invoices on request, consolidated B2C invoices are submitted on schedule, and rejections are queued for finance with the deadline showing.
Do we need asasii pos to use it?
No. asasii commerce runs on its own with the storefront, the marketplaces and the warehouse. With asasii pos, the tills join the same catalogue and stock, and click and collect runs through the outlet console.
Where does it run, and can our other systems talk to it?
In the retailer's own cloud account or data centre. idataraya installs it, hardens it and keeps it current, and the retailer's team holds the keys, the backups and the data. A documented API lets the retailer's accounting system, loyalty programme, asasii pos or a third party read products, stock, orders and settlements and post what they need to.
What does the yearly agreement cover?
Software updates, the customisations made for you, monitoring, severity-based response and restoration targets, storefront updates and marketplace connections. Hosting stays with you. It is a fee, not a percentage of sales.