Public entry points
- Loading...
Shopee Open Platform / seller operations
A clear path from marketplace events to seller operations.
JBSCC is an independent connector for authorized seller workflows. It demonstrates how order, after-sales, fulfillment, inventory, and advertising performance records move through a controlled processing queue before an internal Odoo-compatible sales and warehouse process.
Demo mode: all records in the public demo are synthetic. Production token exchange,
persistent storage, and live ERP sync require approved credentials and an authorized seller pilot.
Integration overview
Everything needed to understand the workflow.
Public entry points, readiness checkpoints, and support details are pulled from the live API.
Readiness checklist
- Loading...
Current integration state
Checking...
Live integration status loads from the public API.
What the integration covers
One workflow, five observable stages.
Each stage has a visible endpoint or operational surface. The demo keeps production prerequisites explicit.
Authorize
Seller authorization returns to a server-side callback. The demo exposes the expected parameters without storing tokens in the browser.
Inspect callback ->Receive events
Order, return, fulfillment, and stock events enter a bounded receiver with payload limits and an idempotency boundary.
View controls ->Map operations
Marketplace order lines map to internal SKUs, warehouses, sales orders, return queues, and operator actions.
Open order mapping ->Reconcile
Stock and status differences are held for control before an update is published back to a marketplace channel.
Open reconciliation ->Advertising
Read-only campaign performance is linked to products, SKUs, related orders, warehouse stock, and ERP targets.
Open advertising ->Requested data scope
Every data category has an operational reason.
| Data category | Operational purpose | Control | Workflow status |
|---|---|---|---|
| Orders and order items | Fulfillment and internal sales order creation | Seller-authorized, server-side processing | Demonstrated |
| Returns and refunds | After-sales processing and warehouse intake | Case queue and operator decision | Demonstrated |
| SKU and stock quantities | Inventory reconciliation and stock accuracy | Mismatch control before push | Demonstrated |
| Advertising performance | Campaign performance, advertising cost reconciliation, and product-level operational analysis | Seller-authorized, server-side processing; attribution fields shown only when provided | Review/demo boundary |
| Webhook metadata | Event processing, replay protection, troubleshooting | Payload limit and idempotency key | Integration boundary |
| Shop authorization tokens | Server-side calls after seller approval | Protected storage required in production | Approval gated |
Security and compliance
Controls are stated as evidence, not decoration.
The public surface is intentionally explicit about the current demo boundary. Production controls activate only after credentials, secrets, persistence, and pilot validation are in place.
HTTPS-only endpoints
ActivePublic site, app, and API are served over TLS.
Server-side OAuth boundary
ConfiguredCallback parameters are received by the API; token exchange is not exposed to the browser.
Replay-safe event boundary
Design-readyEvent identifiers are designed to be stored and checked before processing.
Access and deletion requests
DocumentedPrivacy page provides an operator contact path for data access and deletion requests.
Operator and support
Check the integration status, then contact the operator.
JBSCC Shop Operations is an independent seller-operations application. It is not an official Shopee website or Shopee-owned ERP product.