Architecture, Data Directions, and Status

The connector runs within Business Central, sends HTTPS requests to the Magento REST API, and stores mappings, statuses, and logs in BC.

Data Flow

What Moves Where?

Data Area	Direction	Typical Trigger
Reference data and mappings	Magento → BC	Initial download
Items, variants, categories, images	BC → Magento; partial download	Single action or Cockpit
Inventory	BC → Magento MSI	Single or batch run
Orders	Magento → BC	Cockpit or validated job
Shipment, tracking, invoice	BC → Magento	Document action or batch run
Credit memos	Magento → BC	Download; document creation limited

Typical Process

Download

1. User or validated job starts an area.
2. Preflight checks configuration and dependencies.
3. Magento delivers REST data.
4. BC creates or updates records.
5. Business log and target state are verified.

Upload

1. BC record or batch run is selected.
2. Active status and required fields are checked.
3. The connector generates Magento JSON.
4. Magento creates or updates the target object.
5. ID, timestamp, and message are stored.

Reading Status Correctly

Synced, Synced At, Magento ID, and Status Reason describe the last documented run. They do not prove current parity between both systems.

For important operations, always verify the BC record, the corresponding business log, and the actual Magento state.