Skip to content

Onboarding your data

A new Resolve environment starts with a guided onboarding flow that imports your commercial data step by step and finishes with a priced, publishable book. Each step explains the file format it expects, previews your data as you map it, and validates before anything is committed.

Onboarding is done together with the Resolve team

Initial data onboarding is typically completed with the Resolve team during implementation: file formats, attribute definitions, and price-list structure are agreed against your source systems, so the import steps reflect your own data rather than a generic template. The Resolve team provides the field specifications for each step.

The steps

  1. Settings — choose your currency and how you think about profitability (the Price Display Preference: work in prices, margins, or markups — changeable later at any time).
  2. Locations — import the stores, branches, or regions you price for.
  3. Products — import your product catalogue.
  4. Hierarchy — map products into the category structure that pricing rules will inherit through. You define the levels; Resolve shows the tree as you build it.
  5. Customers (optional) — import customers and their price-list assignments. Skip this if you price a single tier.
  6. Pricing Attributes — import the data pricing decisions depend on: unit costs, competitor prices, MSRPs, or any attribute you define.
  7. Publish — review a summary of everything imported and launch.

Importing files

Each import step accepts a CSV file through the same wizard: upload, match your file's columns to Resolve's fields, review flagged rows, confirm. The wizard tolerates real-world files — column order doesn't matter, and you see exactly which rows need attention before committing.

Bulk data after onboarding

Day-to-day, master data is maintained on the Data Management pages. For recurring bulk loads — nightly cost updates, catalogue refreshes, or keeping Resolve reconciled with your ERP's price book — see ERP & data exchange.

What "good" looks like after onboarding

  • Every product sits somewhere in the hierarchy (unmapped products can't inherit prices).
  • Products you sell have a unit cost attribute, so cost-pegged rules can price them.
  • Locations and price lists reflect how you actually trade.

From here, a first pricing pass is typically one category-level markup rule per major category — minutes of work on the Set Prices matrix — refined product by product afterwards.