Domestic operations
China domestic e-commerce
Coordinate stores, orders, inventory and fulfilment through the appropriate domestic ERP edition.
S-KNIGHTASIAChina e-commerce & cross-border operations
Bring your online orders, inventory and fulfilment into a connected business process.
S-Knight Asia’s proposed OMS offering brings together order management, third-party software and integration services to connect e-commerce operations with enterprise finance and operations—particularly Dynamics 365 Business Central and Finance & Operations—with integration assessed around your requirements.
Illustrative concept · Not a live integration
Start with your operating model
The right solution starts with how you sell, where you hold stock and how your finance team works.
Domestic operations
Coordinate stores, orders, inventory and fulfilment through the appropriate domestic ERP edition.
Cross-border edition
Explore overseas marketplace and fulfilment operations with an appropriate cross-border software edition, including relevant FBA and logistics workflows.
Discovery scenario
Assess how local channels, operating entities, warehouses and enterprise systems could work together.
The commerce ecosystem
Bring sales channels, delivery providers and warehouse systems into the assessment. These selected examples are informed by the underlying software provider’s connection references; availability depends on the chosen edition.
Coordinate store orders, stock and fulfilment around your selected domestic ERP edition. Confirm each platform’s account authorisation and available interface scope.






Assess carrier accounts, shipping services, labels and shipment updates for your fulfilment model. Available functions depend on the carrier and selected software edition.





Examples of warehouse types listed in the underlying software provider’s technical reference. Confirm provider onboarding, warehouse coverage and the exact interface before planning a connection.





Edition, licensing, API access, account permissions and current service availability require assessment. These are OMS-side connection examples; integration with Dynamics 365 remains a separately assessed, proposed solution.
Third-party logos identify the services shown. They do not imply an S-Knight Asia partnership or endorsement. This is a selected directory, not an exhaustive or guaranteed coverage list.The operational foundation
Capabilities differ by edition. Use these areas to shape the assessment, then confirm the functions and access included in your selected product.
Give the team a consistent way to handle orders across stores.
Connect stock decisions with the locations doing the work.
Bring replenishment decisions closer to operational demand.
Make the hand-off from accepted order to warehouse work clearer.
Keep returned goods and related financial records connected.
Help operations and finance work from agreed business records.
Capabilities depend on the underlying software and selected edition. Availability, licensing and platform access require confirmation.
Proposed integration architecture
A proposed integration layer maps selected operational data to your Dynamics system. The design starts with your existing processes and the APIs available to your chosen edition.
Selected channels
and store accounts
Domestic ERP or
cross-border edition
Mapping, validation
and exception handling
Business Central
or
Finance & Operations
Arrows show the proposed process connection. Actual data directions and timing will be agreed during assessment.
API access depends on the underlying software and selected edition. The proposed solution does not assume a ready-made Dynamics connector. Confirm edition, API access, data ownership, direction, frequency, error handling and reconciliation rules before implementation. Cross-border data and regulatory requirements also need assessment.
An order’s journey
A simple example of the process we would map together—from the customer’s order to a finance review.
Order capture
A store order enters the selected e-commerce workflow. Product identifiers, quantities and order references are checked against the agreed mapping.
Assessment question: which system owns the order and product record?
No customer information · No connected systems
Proposed S-Knight Asia services
Bring your e-commerce and enterprise teams into one conversation. Final deliverables, responsibilities and support arrangements are subject to an agreed scope.
Understand your channels, entities, volumes, teams and operational priorities.
Review product fit, licensing, marketplace coverage and available API access.
Agree records, ownership, exceptions and the hand-offs between systems.
Design and build the agreed connections around confirmed technical capabilities.
Test representative transactions, exceptions and financial reconciliation with your teams.
Prepare users for the agreed workflows and define ongoing support responsibilities.
Your questions, answered
The details of your operating model shape the recommendation.
The proposed offering is assessed around third-party domestic ERP or cross-border software editions. We would confirm your precise platforms, store regions and fulfilment models against the selected edition and current vendor availability. Coverage is not universal, and licensing or account permissions may differ.
That is the proposed direction. We would assess your Business Central or Finance & Operations version, deployment, extensions and available interfaces. The architecture shown here is a proposal, not a claim that a ready-made or certified Dynamics connector already exists.
We would agree which system owns each record, what flows in each direction, how often exchanges run and how failures are handled. Timing depends on available APIs, limits, transaction volumes and your requirements; real-time synchronisation is not assumed.
A confirmed edition and licence, platform accounts and permissions, API documentation and access, sample data, test environments and responsible business owners. Entity, warehouse, security, privacy and cross-border data requirements must also be assessed. Customs and tax requirements are not automatically covered by the proposed integration.
After discovery, the scope would account for the selected products, licensing, data mappings, integration complexity, testing, training and support. A commercial proposal and delivery plan would follow an agreed assessment; no fixed price or delivery date is implied here.
S-Knight Asia’s proposed role covers requirements assessment, process mapping, integration, testing, training and support. OMS describes the solution category; underlying software, licensing, procurement and delivery responsibilities would be confirmed during discovery.
Let’s start with your operations
Start with your selling channels, warehouse processes and existing Dynamics environment. We can then assess the next connection together.