feedsteadOpen the workspace →

Saving and reusing supplier mappings

A saved mapping is a repeatable instruction set for one supplier/client workflow. It should record the decisions that otherwise live in a spreadsheet checklist or in one operator’s memory.

Worked example

Configuration name: Sample supplier → Sample catalogue

Setting Saved value
Supplier SKU column Product code
Supplier cost column Net cost
Decimal convention decimal point
Currency USD
Review threshold 25%
Supplier list type Partial update
Markup 50%
Rounding nearest cent
Client profile Sample catalogue

Exact SKU text matching is always on.

Start the next client update

Open Client profiles and choose Use beside the supplier configuration. Feedstead starts a new update with that client's saved mapping and rules. If you already have files loaded, you can keep the current update or confirm that you want to clear it. Your saved configurations remain available.

Add a fresh Shopify export and the latest supplier price list. The client and selected configuration stay visible above the source files. If a saved column is missing from the new supplier file, Feedstead identifies it and requires you to select the correct column before comparison. Check sample values and confirm the pricing assumptions for each new pair of files.

When rules change, choose Save configuration, review its name, and choose Update configuration. This replaces the selected configuration without using another slot. To keep both versions, select Save as a new configuration and give the copy a distinct name.

A saved configuration reduces setup work; it is not proof that the supplier's format has remained stable. Files, comparisons and selected rows are not stored in the configuration.

Reuse checklist

Backup and restore

Workspace subscribers can export and import a local configuration backup. Keep the backup in a location appropriate for client operational data. Feedstead does not store source supplier files; a configuration backup may still contain business rules and field names, so handle it according to the client’s data policy.