Selling on SHEIN while running Dynamics 365 Business Central usually means two systems that never agree. Orders arrive in the SHEIN seller portal and get keyed into Business Central by hand or dropped in through a spreadsheet, so the order date, the marketplace order number and the customer reference drift apart. Available inventory in Item Ledger Entry is the truth, but SHEIN only knows what someone last uploaded, so the same unit gets sold twice and a cancellation follows. At month end the settlement report lands as a file of gross sales, commission, logistics charges, returns and adjustments, and nobody can reconcile it against posted Cust. Ledger Entry records without a week of manual work. Business Central has no marketplace concept out of the box: no channel order staging, no SKU-to-listing mapping, no place to hold a marketplace fee that is not a vendor invoice.

ECOSIRE builds a dedicated AL extension for your tenant that treats SHEIN as a first-class sales channel inside Business Central. A SHEIN Setup page holds credentials, endpoint region, shop identifiers and posting defaults; secrets go into isolated storage, never a plain table field. Codeunits handle authentication and signed requests with a retry and backoff policy and a per-call log, so a failed pull is visible rather than silent. Marketplace orders land first in a staging table with the raw payload attached, then map to sales orders through a configurable SHEIN Order Status Mapping table so awaiting-shipment, shipped, cancelled and returned states each drive the right document action. SKU mapping lives in its own table linking SHEIN listing and variant identifiers to Business Central Item No. and Variant Code, with unit-of-measure and barcode handling so a multi-pack listing does not decrement one piece.

On the outbound side, event subscribers on inventory and price changes queue delta updates rather than re-pushing the whole catalogue, so a posted receipt or a Sales Price change reaches SHEIN within the next job queue cycle instead of overnight. Listing export builds the payload from item attributes, item category and configurable attribute mapping, so category-required fields are populated from data you already maintain rather than retyped. When a warehouse shipment or sales shipment posts, a subscriber pushes carrier, tracking number and shipment lines back to SHEIN and stamps the confirmation on the order.

Settlement files and settlement API responses are imported into a reconciliation worksheet where each line is matched to its order, the commission and logistics components post to the G/L accounts you nominate through a SHEIN Fee Mapping table, and the net payout is proposed as a journal that a finance user reviews before posting. Everything runs on Job Queue Entry records with distinct categories so you can tune frequency per flow, and API pages expose the staging and mapping data over REST API v2.0 / OData v4 for Power BI, Power Automate or a Dataverse virtual table if you want the channel visible outside Business Central. Dedicated permission sets separate the setup role, the operations role and the finance reconciliation role.

This is build-to-order, not an AppSource download. After a scoping call we confirm your SHEIN shop regions, order and returns flows, warehouse and shipment setup, fee posting policy and any existing marketplace extensions in the tenant, then produce a written scope naming the exact objects, mappings and edge cases. We build against your Business Central version, deliver as a per-tenant extension to a sandbox first, run UAT with your own orders and a real settlement file, and only then publish to production with a rollback plan. Typical delivery is two to four weeks from confirmed scope. You receive the AL source and the git repository, so the extension stays yours whether or not you keep working with us.