CP Commerce
“Can I run my own storefront?” Yes. A website and mobile app your customers browse, register, order and book on is configured in one applet, CP Commerce Admin, and the orders it takes arrive as ordinary sales documents. That applet’s page is the reference for every screen in it. This folder holds two features of it that needed a page of their own: push notifications to the mobile app, and the shopper claiming their own e-invoice.
Which page answers your question
| You want to… | Read |
|---|---|
| Set up a storefront: its pricing, menus, sign-in buttons, shipping, legal agreements, which customers may see it | CP Commerce Admin — every tab of the Website record |
| Lay out the pages and choose what each one shows | Layout Instance and the widget reference |
| Let a store manager change the shop without opening the console | The Webstore dashboard and Website Builder |
| Send a message to everyone who installed your app | Push Notification Configuration — the success message does not prove a send |
| Let a shopper ask for their own LHDN e-invoice from the website | Storefront E-Invoice Request — it takes the sale out of your monthly consolidated e-invoice with no approval step |
| Cap what a B2B buyer orders | Spending Limits, then the Customer record: the rule here blocks nothing |
| Take bookings for rooms, classes or events | Activities and Facilities |
| Change what a product costs or how it is described | Doc Item Maintenance, Pricebook — the storefront owns no product data |
| Find an order a customer placed, or the payment for it | Shopping Cart, then E-Commerce core concepts §2 and §4: a sales order with the payment as a settlement line, no receipt voucher |
| Sell on Lazada, Shopee, TikTok Shop or Shopify | EcomSync Related Applets, not this applet |
What a storefront is made of
Three records have to agree before a shopper sees anything, and BigLedger keeps one of them for you.
- The Host Name record for your domain, which BigLedger keeps. The storefront looks up the address it
was opened on and reads three values: a public key that authenticates everything a guest does, your
tenant, and which Website to show — so the domain decides the website. A record missing one of them
stops the storefront before its session starts, with the error (*“Configurations of: … for Hostname: …
- has not been configured”*) only in the browser’s developer console; the shopper sees no message.
- The Website record, yours, in CP Commerce Admin. It needs a branch and a membership class before it saves; its Pricing decides whose prices the shop shows, and its Status whether the shop is served.
- A branch in Organisation, which the website is attached to (core concepts §5).
Push notifications also need a Firebase credential on the website, which BigLedger support places there; the e-invoice widget needs your company already set up for e-invoicing. Nothing in CP Commerce Admin posts, and a save is live — build a new storefront on a second website record and switch it Active when it is ready. What runs after a checkout, and the three CP Commerce clocks no new tenant is given, are on the console page’s What actually happens later.
Where the figures come from
| Figure | What it is | Read |
|---|---|---|
| A product’s price | Looked up when the page loads, from the scheme or price book the website reads | CP Commerce Admin › Pricing |
| Published successfully on a push | Proof only that the button was pressed | Push Notification Configuration › Troubleshooting |
| The shopper’s In Queue count | Includes requests that already failed | Storefront E-Invoice Request |
| Customers viewed this item | What it counts | CP Commerce Admin › Product views |
When something goes wrong
Start at the admin troubleshooting (a saved website customers cannot see, a missing or wrong price, a spending-limit rule that never fires), push notification troubleshooting or Storefront E-Invoice Request › The public key is the whole guest path (every search failing; a sale in neither e-invoice). For the Host Name record, ask BigLedger and name your domain. The product tells nobody when something fails, so run the console page’s weekly check.
Where CP Commerce sits
A storefront needs a branch and merchant, a membership class, priced items, settlement methods and the Host Name record first (Before you can use it). Its siblings are a marketplace shop (EcomSync), the Content Management System (the same menus and posts, no website selector, unaudited here) and the MY E-Invoice Portal (the same e-invoice request from a buyer’s own account). Two settings break things elsewhere: changing the branch of a website that prices by branch repoints the whole catalogue, and a spending-limit rule written as a monthly budget never fires. The job that is not software — stock to show, cancellations, returns and disputes — is Running an Online Channel.