ROME Intelligence
POS export guides
ROME normalizes POS exports into one model — SpotOn is pre-mapped; other systems are mapped during onboarding from your exports. Here's how to produce yours. These are guides for pulling the exports your system already makes, not a list of what's 'supported': ROME is POS-agnostic by design, and building your system's mapping is part of onboarding. Pick your system below, or send a sample export and we'll confirm fit in one email.
What ROME needs from your POS
- Sales / orders — Checks or orders with date & time, and check-level fields like guest count, subtotal, and total.
- Order items — The line items on each check — item name, quantity, price, and line total.
- Menu & costs — Your menu items with prices, and plate/food costs if you track them — costs unlock the margin math.
- Labor / timecards — Shifts or punches — date, role, clock in/out, hours, wage, and labor cost.
Date range: 120+ days is ideal (it captures weekday patterns and seasonality); 90 days works; even 30 days produces a useful first read.
Guides by system
Ready-made mapping
SpotOn
The exact files and columns ROME ingests — our input contract, documented column by column.
Read the SpotOn guide →General guidance
Toast
What to export and where to look — plus the official Toast documentation.
Read the Toast guide →General guidance
Square
What to export and where to look — plus the official Square documentation.
Read the Square guide →General guidance
Clover
What to export and where to look — plus the official Clover documentation.
Read the Clover guide →General guidance
Aloha
What to export and where to look — plus the official Aloha documentation.
Read the Aloha guide →General guidance
Future POS
What to export and where to look — sales, order items, menu and costs, and labor.
Read the Future POS guide →Have your export? Book a walkthrough →