ROME Intelligence
Exporting your data from SpotOn
SpotOn has ROME's ready-made mapping today — this page documents the exact files and columns our ingestion pipeline reads. It's our input contract, rendered from the same code that validates your upload. (ROME normalizes POS exports into one model — SpotOn is pre-mapped; other systems are mapped during onboarding from your exports.)
The two exports ROME reads
1. Item-level sales export — one row per order line, with the check-level fields (order id, date, time, guest count, subtotal) repeated on each row. This drives the audit, menu engineering, forecasting, and customer analysis.
2. Labor / timecard export — one row per shift or punch. This drives labor-cost analysis, staffing findings, and the right-staffing plan.
The columns that matter
Sales export
Required columns
Order ID · Business Date · Opened At · Guest Count · Check Subtotal · Item ID · Item Name · Category · Quantity · Unit Price · Line Total
Optional (used when present)
Location ID · Customer ID · Unit Cost · Discount Amount · Discount Type · Tender Type
Labor export
Required columns
Business Date · Role · Clock In · Clock Out · Hours · Hourly Wage · Labor Cost
Optional (used when present)
Shift ID · Location ID · Overtime
Dates may be YYYY-MM-DD or M/D/YYYY; times may be 24-hour or AM/PM — the pipeline normalizes both. Rows that fail validation are counted and reported, never silently dropped, and re-uploading the same file is safe (duplicates merge cleanly).
Date range
120+ days is ideal (it captures weekday patterns and seasonality); 90 days works; even 30 days produces a useful first read.
How to send it
Reply to any email from the team with the CSV files attached, or start from the Book a walkthrough formand we’ll take it from there. If your export’s column names differ from the lists above, send it anyway — header variations are usually a five-minute mapping on our side.
Have your export? Book a walkthrough →