E-Commerce

Configuration screens inside the CP Commerce admin console, documented one screen at a time

Settings screens inside the CP Commerce Website Builder that write to the platform, not only to the site

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