Incremental fitment exports
An incremental fitment export sends complete current fitment for selected products whose export inputs have changed since their last successful delivery. It is optional: existing fitment exports do not change unless fitment_export_diff is enabled. Product diff_fields does not enable fitment change detection.
The mode supports one compatible file configuration with no actions, calculations, formatting, or catalog EPID lookup. Set positive limits for complete products and output rows:
{
"fitment_export_diff": true,
"fitment_export_max_items": 50,
"fitment_export_max_rows": 100000
}
These values illustrate the shape, not recommended limits. Choose them based on your data and your recipient's capacity. The item limit counts complete emitted SKUs; the row limit excludes the header. If the row limit would be exceeded, the run stops before delivery and does not advance its comparison baseline. A single SKU that exceeds the limit requires separate handling.
On the first run, matching products are included up to the configured item limit. Later successful runs skip unchanged delivered products and process remaining matching products. Use a stable selection: a rolling date cutoff can exclude products waiting to be exported. Each emitted SKU contains its complete current fitment, including unchanged rows.
A debug run does not use or advance the saved comparison baseline. A full run or diff_update: false bypasses comparison but still applies the limits and advances the baseline after successful live delivery; repeated full runs are not a way to drain a backlog. A failed send does not advance the baseline. In some failure cases data already sent may be sent again, so the recipient should handle replacing the complete fitment for a SKU idempotently.
This mode does not establish deletion or identity-change handling at the recipient. A product that loses its last fitment emits no row; removing a SKU from the selection or changing its identity does not remove the old record at the recipient. Agree on a separate process for those cases. Changes only to external vehicle reference data are not detected by the product-input comparison.
Before scheduling, test a representative initial export, a change, a repeated run, and the recipient's handling of repeated data. Monitor whether the export keeps up with changes. A successful send confirms delivery through the configured connection, not that the recipient imported or accepted the data.