Related Applets
The module’s own twelve applets are listed on the module page. This page is the rest: the applets in other modules that the e-commerce workflow cannot complete without, each linked to the module that owns it, and what e-commerce hands back.
The marketplace screens live in three applets other modules own
This is the fact that makes the E-Commerce module look smaller than it is. EcomSync is not an applet; its screens are tabs and menus in:
| Applet | Owner | What it holds |
|---|---|---|
| Organisation — Branch → Marketplace | Core | The marketplace branch: type, authorisation, stock rule, settlement, pricing scheme, publish queue |
| Doc Item Maintenance — Marketplace tab, Ecomsync Management, Scheduler | Core | Listings per shop, category / brand / logistics pulls, the Lazada and Shopee job schedules |
| Sales Order (Internal) — Ecomsync menu and tab | Sales | Ingested marketplace orders, the dashboards, review replies, the bulk status update |
The EcomSync Related Applets page is the index across the three.
From Core
| Applet | Why e-commerce needs it |
|---|---|
| Organisation | The branch a website is attached to; the marketplace branches; the company’s Knock Off Configuration, without whose Shopping Cart → Sales Order row a FINAL cart goes nowhere |
| Merchant Admin | The merchant entity behind a website (gateway credentials the callbacks are verified against), and behind every seller; the contracts and rate cards the monthly merchant report prices |
| Doc Item Maintenance | The items, their main image and dimensions, the service item a shipping fee is written to |
| Pricebook | The pricing scheme a website’s pricing model points at; the marketplace branch’s default scheme; the seller pricing schemes that decide seller allocation |
| Customer Maintenance | The customer entity a cart belongs to; the login link that scopes the Customer Access applet; the entities a gated B2B website is restricted to |
| Cashbook | The settlement methods a website and a country offer, and a marketplace branch’s settlement method. The Shopee payout job does not use that one: its cashbook is set on its own schedule |
| Tax Configuration | The tax codes on cart and order lines |
From Sales
| Applet | Why |
|---|---|
| Sales Order (Internal) | Where every online order ends up, by conversion, knock-off or ingestion; the Ecomsync screens; the SO reports |
| Sales Invoice (Internal) | The first document in the online chain that posts and moves stock (quantity −1, amount +1) |
| Sales Report | The only place online revenue appears |
| Delivery, return and credit-note applets | The rest of fulfilment; see that module’s page |
From Inventory
| Applet | Why |
|---|---|
| Stock Availability | The item’s stock by location, which each shop’s figure starts from. The shop’s own figure is not here: it is the Balance on the item’s Stock Availability tab in Doc Item Maintenance |
| Stock Reservation | The only way stock is held for an online order; nothing in e-commerce reserves as a side effect |
| Stock Balance | The balance the availability job starts from |
From Financial Accounting
| Applet | Why |
|---|---|
| Receipt Voucher (Internal) | What a marketplace payout becomes, written by its job. A storefront checkout’s payment is not one: it is a settlement line on the sales order |
| Bank Reconciliation | The only place payouts and gateway settlements are matched to the bank; there is no e-commerce settlement report |
| Chart of Account | The cashbook and debtor accounts the receipt voucher resolves against |
From Membership
| Applet | Why |
|---|---|
| Membership Admin | The membership class a website requires; the classes a Spending Limit is set per; the points a member pays with |
| Voucher Management, Commission Scheme | Linked to a website on their own tabs in CP Commerce Admin |
From CRM
| Applet | Why |
|---|---|
| Events Management | The fuller event workflow. CP Commerce Admin’s own Activities group covers facilities, activities, calendars and scheduling for the portal; Events Management holds the event records. It has no landing-page builder, ticketing, QR check-in or surveys, and no e-commerce page may credit it with them |
What E-Commerce supplies to other modules
- Sales orders to Sales — from the storefront by conversion or knock-off, from the marketplaces by ingestion.
- Receipt vouchers to Financial Accounting — from marketplace payouts, by job. A storefront checkout’s payment goes as a settlement line on the sales order, which the cashbook posting job, where it runs, posts to the cashbook.
- The marketplace availability figure to Inventory, computed from that module’s balances.
- Seller orders to the marketplace tables, which the Seller Applet exposes to the seller.
- The monthly merchant report’s inputs — payment transactions with their charge lines — to Merchant Admin’s report processor.
What it does not supply: journals, stock movements, approvals, or a gateway-fee posting. Those are, respectively, the invoice’s, the invoice’s, nobody’s, and finance’s.