Imports and exports
An import reads information from another system and applies the configured changes in SureDone. An export selects SureDone records and sends the resulting data to another system. The connection and file configuration together determine what is exchanged and how it is processed.
Importing products
Choose an identifier that matches your supplier's data to the intended SureDone products. The default is guid. You may use identifiers for ordered priority matching. Review the mapping and choose the intended create, update, or remove behavior before enabling the import. Product updates may use edit or relist; the correct choice depends on whether the product needs to be listed again on connected channels.
For product imports, skip_channels and skip_all can prevent selected channel updates. import_media controls importing media URLs, and force permits updates to protected fields. Do not assume these skip settings prevent every external effect of an order or shipment update. These options affect downstream behavior, so test them with a small representative sample.
diff_update defaults to true unless the run overrides it. With diff_fields, the import compares the listed fields; without a list, other changed fields can trigger an update. diff_tolerance can set a tolerance for supported comparisons.
missing_vendor_items can apply zeroStock, end, or delete to items absent from the source. This can affect many products. Confirm the source is complete and the automation's scope is correct before using it.
Exporting products
Use search to select products and field_map to choose and name output fields. headers controls whether a header row is included. delimiter defaults to a comma. A template can be used for supported custom output formats.
Product exports can use diff_fields to send products whose listed fields differ from the last successful export snapshot. Products with no snapshot are included. A full run or diff_update: false includes all matches and advances the baseline after successful delivery. Debug runs do not use or advance snapshots. diff_tolerance does not apply to these export snapshots. Avoid using response writeback targets as diff fields; the writeback can cause a product to be included repeatedly.
Delivery to a connection does not itself prove that the receiving system imported or accepted the data. Confirm the result in the receiving system when acceptance matters.
Orders and tracking
For order imports, the default order identifier is oid; order_item_identifier defaults to sku for matching existing order items. Choose the correct order and item identifiers for the incoming data and test with representative multi-item orders.
split_tracking_by_comma can split a comma-separated tracking value into separate shipment records. The optional order_tracking_groups feature supports a complete vendor-order tracking response. It requires an order import with update: true, identifier: "oid", order_item_identifier: "itemid", payload_multi: false, and a nonempty order_update_search. It cannot be combined with create or remove operations, other data parsers, actions, value maps, field formatting or calculations, comma splitting, or line-item payload mode. The response must contain the relevant vendor orders, and each vendor part must match exactly one eligible order line. Validate the complete configuration and test it with the supplier's actual response before use.
When actual package item quantities are available, a nested packages mapping can preserve them. Do not combine package mapping with split_quantity_across_tracking. The latter estimates how to distribute units when actual package contents are unavailable; those estimates are not proof of what was packed in each box. Coordinate competing imports that affect the same orders.
For order exports, order_payload_line_item exports items separately. With an item-field search, order_payload_line_filter can exclude nonmatching items. order_payload_include_items makes sibling items available to line-item templates; those items are not automatically restricted to the selected vendor, so templates must apply the desired scope.
Use a test run and inspect the resulting records and the receiving system before enabling an ongoing schedule. A test run may still contact the connected service, so check its effects and permissions before running it.