Import Everything

Your data already exists somewhere. Bring it in — in bulk, on your terms.

Conveyor line of incoming boxes representing data intake

Match on your columns, not ours

Every importer opens with the same idea: you choose what identifies a row. Match on keys when you have them, or on the fields you actually possess — UPC and ID, planogram name, store number. The importer tells you what a given match means: which rows will update, and whether anything can be created.

Files can be Excel or tab-separated text, multiple files import together when their columns agree, and blank phantom rows — Excel's specialty — are recognized and skipped instead of tripping errors.

Pallets being received and checked in at a dock

Planograms in, library built

Import planograms and C.A.R.M. Studio harvests the products on them — a working product library materializes from files you already have. Performance imports match by keys, by planogram fields, by store alignment, or broadcast a product's values across a whole folder.

Fixtures, positions, drawings, stores, warehouses, alignments, markets: each has a dedicated importer with the same column-matching model, so the second importer you learn feels like the first.

Organized inventory after intake

Sales in at full speed — performance out the other side

Sales history loads at tens of thousands of records per second: select multiple files at once, Excel or tab-separated, with no size limit on text files. Each record carries a store’s week in full — sales, volume, low and high days, weekend volume, and markdowns — keyed by store, year, week, and product, so re-imports update cleanly instead of duplicating.

Then the Performance Populator turns that history directly into planogram performance — weighted averages, ranges, and match-level aggregation — a pipeline most teams spend a week rebuilding by hand every relay.

Checkout conveyor capturing sales at the register

Everything you can import

  • Planograms — with automatic product harvesting into the library
  • Products from Excel, Space Planning libraries, or planogram files
  • Sales history — multiple files at once, tens of thousands of records per second, weekly store detail down to markdowns
  • Performance — keyed, field-matched, store-aligned, or broadcast per product
  • Planogram, position, and fixture properties from spreadsheets or text files
  • Drawings — matched drawings update, unmatched create
  • Stores, store features, and warehouses
  • Store alignments at category and relay level
  • Markets, regions, and areas
  • Multi-file imports with matching column structures
  • Column matching with clear update-versus-insert behavior
  • Duplicate-match detection that stops ambiguity before it saves
  • Phantom-row and blank-line tolerance in Excel and text files