Skip to content

E-Commerce

“Can I run my own storefront?” Yes, and you can sell on Lazada, Shopee, TikTok Shop and Shopify beside it. Both kinds of order land as ordinary sales orders. The applets in this folder are the storefront’s console and its content, the carts, and the seller and marketplace desks. None of them posts to stock or the ledger. Each page listed at the foot is the reference for one applet; the E-Commerce module explains the whole channel.

Which applet answers your question

You want to…Open
Set up your own website and app: pricing, menus, layouts, sign-in, shipping, who may see itCP Commerce Admin, and the CP Commerce folder for push notifications and the shopper’s own e-invoice
Let a store manager change the shop without the consoleWebsite Builder
Put images, videos and PDFs on the siteMedia Library — a file shows only when shared Anyone with the link
Work the carts staff keyed and turn them into ordersShopping Cart (Internal)
Let a customer key their own cart from their own loginShopping Cart Customer Access (Internal) — its FINAL is refused today, so staff finish those carts
Let other businesses sell through your channelSeller Applet
Give one person a Lazada and Shopee order deskTiktok Sales Order Applet — the same sales orders, a shorter menu, nothing TikTok-specific
Connect a marketplace shop and choose what stock it is shownEcomSync Related Applets, not this folder
Know where an online figure came fromE-Commerce › Reports
Edit menus, posts and categories with no website selectorContent Management System — prefer CP Commerce Admin; a theme saved here never reaches a website
Plan how many of each category an outlet displaysPDG Applet — an in-store display plan; it does not feed the storefront

What happens behind the screen

Nothing in this folder posts. A cart and a sales order both carry zero quantity and zero amount; the first document in the online chain that reaches the ledger and the stock ledger is the sales invoice, so an online sale missing from the P&L has not been invoiced yet. An online purchase reaches a sales order by a paid storefront checkout (the server converts the cart; the payment is a settlement line, no receipt voucher), a cart staff finalised (seen by the Sales Order applet only through a Shopping Cart → Sales Order knock-off row), or a marketplace order job (no cart; numbered and FINAL, keyed by nobody) — core concepts §1, §2 and §4. What must exist first, and the settings whose mistakes reach Sales and Inventory, are in Reports, where these figures sit.

When two applets seem to do the same job

Shopping Cart (Internal) or Customer Access, CP Commerce Admin or Content Management System, Tiktok Sales Order or Sales Order (Internal): each page’s Overview says which to use. A marketplace shop is you selling on Lazada or Shopee through EcomSync; a seller is another business selling through your channel, settled by ordinary purchase invoice and payment voucher.

When something looks wrong

Start from the figure in E-Commerce › Reports, when a number is wrong, or from the page that owns the screen: Shopping Cart (a FINAL cart missing from Search Shopping Cart), Customer Access, CP Commerce (a website customers cannot see), Media Library (an image that does not load), Running an Online Channel, Step 2 (less stock on a shop than the shelf), Tiktok Sales Order and Seller Applet. None of these applets reserves stock, records a TikTok payout or a gateway fee, brings in a platform’s return, or tells you when something fails (what has no report).

How you know an online order reached your books

This takes a few minutes. Run it after any change to the website, a marketplace branch or Knock Off Configuration, and once a week otherwise.

  1. Place one order on your website as a test customer and pay through the gateway. Find it in the Sales Order listing, with a settlement line carrying the gateway’s merchant reference. No receipt voucher should appear.
  2. Pick one order from the seller centre of each marketplace and find it on that marketplace branch, numbered and FINAL.
  3. Invoice one of them, and trace that invoice in Trace Document, under Error Checking: its journal should be there. Run the Sales Report for the branch: the invoice is in it, and the order alone never was.

An order missing in step 2 is a feed that stopped, and the EcomSync troubleshooting table starts there. Write down who runs this check. The product does not assign it.

A worked weekend — one phone sold on the website and on Shopee, then cancelled — is on Shopping Cart.

Where to go next

Every page in this section

CP Commerce section
Which page answers your storefront question: the CP Commerce Admin console, push notifications and the shopper's e-invoice request. What a storefront is made of, what runs behind it with nobody pressing a button, where its figures come from, what goes wrong and how to check it works.
Which page answers your Website Builder question: giving a store manager access, taking it away, a missing tile, the console button that opens nothing. What decides whether the Website Builder opens for a person, what the WEBSITE BUILDER button needs first, what goes wrong and how you check the person you promoted can work.
Reference for the CP Commerce Admin applet: the tenant-side console that configures Customer Portal websites and mobile apps — pricing, menus, layouts, sign-in providers, forms, notifications, spending limits, facilities and events — its menus, every configuration screen, fields and known failure modes.
Tenant-wide file store for the Customer Portal: drives, directories and files with a per-file share policy, plus the file categories the CP Commerce storefront widgets read — what each screen does, what is inert, and which backend rules apply.
Reference for the Content Management System applet: five flat editors — Theme, Content Category, Widgets, Menu, Pages — over the CMS tables that CP Commerce storefronts read, with no website selector, no settings screen and no posting.
Reference for the Tiktok Sales Order Applet: a marketplace-oriented build of Sales Order (Internal) that edits the same INTERNAL_SALES_ORDER documents with a shorter sidebar, no settings screens, and Lazada / Shopee dashboards — what it keeps, what it drops, and where its name came from.
Seller-side workspace of the marketplace module: a login linked to a merchant entity maintains that seller's marketplace products and store stock balances, sees the seller orders allocated to it from the tenant's sales orders, and edits the purchase invoices and payment vouchers used to settle with the seller.
Reference for the PDG applet: head-office Product Distribution Guides (recommended display quantity per outlet size, outlet type and product category), the per-outlet OPDG copies that outlet managers adjust, brand-corner splits, the Excel import, the OPDG report, every setting that actually works, the asynchronous create/update job and known failure modes.
Back-office listing and editor for INTERNAL_SHOPPING_CART documents — carts raised by staff, by customer logins, or by CP Commerce storefront checkouts — with FINAL and delete, no posting
Customer-login twin of the Shopping Cart (Internal) applet: a customer whose login is linked to their customer record keeps one INTERNAL_SHOPPING_CART, edits it, prints it, discards it, and submits it — the submit converts the cart into a FINAL Sales Order on the server

8 pages and 2 sub-sections — this list is read from the folder when the site is built, so it cannot fall behind what is in it.