toast

Toast export files explained: Item, Modifier, PMIX, Order, and Payment

Jun 23, 2026

Toast provides report downloads and configurable nightly data exports. The file names sound related, but each answers a different operational or financial question.

The problem

Spreadsheet errors often begin before a formula is written: the wrong file is used for the question. Product Mix is treated as row-level sales. Payment rows are joined directly to menu items. Modifier rows are stacked under item rows.

Start by naming the grain: what does one row represent?

Example Toast CSV columns

Export	One row usually represents	Useful examples
Item Selection Details	One menu-item selection	Item ID, date, item, quantity, net price
Modifier Selection Details	One modifier selection	Parent item ID, modifier, quantity, value
Product Mix	An item aggregate for a period or breakdown	Menu, group, item, quantity, sales
Order Details	One order	Order ID, opened/closed times, dining option
Payment Details	One payment	Payment ID, order/check ID, type, amount
Menu	Menu configuration data	Item, group, identifiers, active state

Toast allows configured nightly exports to choose column names and order. Never assume every restaurant receives the same schema.

Which file should you use?

“What sold?” Start with Item Selection Details.
“Which add-ons were selected?” Add Modifier Selection Details.
“What is the item mix for a period?” Use Product Mix.
“How were orders opened, closed, or categorized?” Use Order Details.
“How was money tendered?” Use Payment Details.
“How is the menu configured?” Use Menu data.

When a question crosses grains, define the join and reconciliation before combining files.

Screenshot and demo

FoodSaver upload screen for supported Toast CSV exports

FoodSaver requires Item Selection for the clean item workbook. Other supported files are optional; Product Mix, Order, Payment, and Menu are currently preserved as sanitized source sheets rather than fully normalized semantics.

Free sample workbook

The sample files make the item-versus-modifier grain visible before you use restaurant exports.

Pricing

FoodSaver offers three free successful generations per UTC day within free limits. Pro costs $19/month or $190/year and adds larger files, history, saved mappings, email delivery, and 90-day retention.

See plan details.

Frequently asked questions

Are nightly exports the same as manual report downloads?

Toast says nightly data exports cover many of the same data types available from Toast Web, but configured columns and timing can differ.

Can I combine every export in one worksheet?

Use one workbook, not one undifferentiated table. Separate sheets preserve row grain and reduce accidental duplication.

Why does my coworker’s export have different columns?

Configured exports can choose column names and order. Report filters and versions can also affect downloads.

Which file does FoodSaver require?

Item Selection Details. Modifier Selection is optional but needed for item-modifier detail.

Sources

Next: compare Toast SFTP with manual CSV exports.

Try the free Toast Prep + OneCSV workbook generator.

MarginEdge alternative for small restaurants: full platform or focused workbook?

Jun 23, 2026

MarginEdge and FoodSaver solve problems at very different depths. MarginEdge is a broad restaurant management platform. FoodSaver is a focused Toast export cleanup and workbook tool.

The problem

“MarginEdge alternative” can mean “I need another complete back-office system” or “I do not need a complete back-office system yet.” Small restaurants should separate those questions before comparing monthly prices.

What MarginEdge includes

MarginEdge’s official pages describe invoice processing, bill pay, inventory, recipe management, price alerts, ordering, daily reporting, and comparisons of purchases, sales, inventory, and waste.

Its public pricing page listed $350 per location per month for MarginEdge and $500 per location per month with the Freepour bundle when reviewed on June 23, 2026. The same page notes additional Toast subscription requirements for Toast API integrations. Verify current pricing and terms directly before purchasing.

What FoodSaver includes

FoodSaver handles a narrower workflow:

select supported Toast CSV exports;
preview and confirm file types;
confirm required columns;
create exact item-modifier joins;
keep exceptions and source references visible;
generate an Excel workbook for review.

It does not process invoices, pay bills, maintain inventory, manage recipes, or calculate a daily P&L.

Example Toast CSV columns

item_selection_id,business_date,item_name,quantity,net_price
item-204,2026-06-22,Burger,1,10.00

This is enough to begin an item-level sales review. It is not enough for actual food cost, because that requires purchasing, recipe, inventory, and waste data.

Decision table

Primary job	Better fit
Invoice capture and coding	MarginEdge-class platform
Bill pay and accounting sync	MarginEdge-class platform
Inventory and recipe management	MarginEdge-class platform
Purchase-versus-sales usage analysis	MarginEdge-class platform
Clean Toast exports into Excel	FoodSaver or manual Excel
Validate a recurring cleanup workflow cheaply	Start focused

The larger platform may be better value when several modules replace real labor. The smaller tool may be better when only one annoying workflow has been validated.

Screenshot and demo

FoodSaver workbook exception preview with synthetic Toast rows

Open the FoodSaver demo to test the narrower workflow before treating it as a platform comparison.

Free sample workbook

Pricing

FoodSaver includes three free successful generations per UTC day within free limits. Pro is $19/month or $190/year. MarginEdge’s official page listed the per-location prices above as of June 23, 2026; confirm current pricing and integration costs with MarginEdge.

See FoodSaver pricing.

Frequently asked questions

Is FoodSaver a MarginEdge replacement?

No. It replaces only a narrow manual export-cleanup task, not the broader back-office platform.

Which is better for inventory?

MarginEdge documents inventory, recipe, purchasing, and usage capabilities. FoodSaver does not currently provide inventory management.

Why compare them at all?

Because a restaurant searching for an alternative may be deciding between a full system and a smaller validated workflow, not between identical products.

Can Toast CSVs produce actual food cost?

Not alone. Actual food cost needs purchases and inventory; theoretical usage also needs maintained recipes and PMIX mappings.

Sources

Also compare the xtraCHEF alternative decision.

Try the free Toast Prep + OneCSV workbook generator.

Toast modifier sales report cleanup in Excel

Jun 23, 2026

Modifier cleanup is not just deleting blank rows. The goal is a table where each modifier remains traceable to its source and its parent item—or is clearly marked for review.

The problem

Toast modifier data can contain repeated names, zero-priced choices, paid add-ons, special requests, voids, malformed values, and parent IDs that do not exist in the chosen item file. Removing “messy” rows can make totals look neat while destroying the audit trail.

Example Toast CSV columns

business_date,parent_item_selection_id,modifier_group,modifier_name,quantity,net_price,voided
2026-06-22,item-204,Cheese,Extra cheese,1,2.00,false
2026-06-22,item-999,Add-ons,Avocado,1,2.50,false

Keep these cleanup columns beside the normalized values:

source filename;
source row number;
parent match status;
parse warning;
voided status;
review note.

Cleanup sequence

Preserve the untouched CSV.
Normalize whitespace without changing the source field.
Parse quantity and currency explicitly.
Keep zero values distinct from blanks and invalid text.
Check whether each parent ID matches exactly one Item Selection.
Mark unmatched and ambiguous relationships.
Keep voided rows visible.
Build modifier frequency and value summaries from reviewed rows.

Do not deduplicate repeated modifier names automatically. Two “Extra cheese” rows may represent two deliberate selections.

Screenshot and demo

FoodSaver workbook preview showing unmatched and voided rows

The exception sheet is part of the deliverable, not a failure screen.

Free sample workbook

Use the synthetic item-999 row to test how your process handles an unmatched parent.

Pricing

Generate up to three successful workbooks per UTC day for free within the free limits. Pro is $19/month or $190/year and adds larger limits, saved mappings, history, email delivery, and 90-day retention.

Compare plans.

Frequently asked questions

Should zero-priced modifiers be removed?

No. They may represent included choices or operational preferences. Keep them for frequency analysis.

Can I deduplicate by modifier name and check number?

Not safely. One check can include multiple identical items and modifiers.

Should voided modifiers count?

Keep them visible and decide explicitly which analysis excludes them.

Why preserve invalid raw values?

They show what the source contained and make correction possible without guessing.

Sources

Try the free Toast Prep + OneCSV workbook generator.

Toast PMIX to prep list: a practical spreadsheet workflow

Jun 23, 2026

Toast Product Mix can anchor a prep worksheet, but it cannot answer “how much should we prep?” by itself. The useful workflow preserves the sales history and makes every operator assumption visible.

The problem

PMIX counts sold menu items. Prep lists call for pans, pounds, quarts, batches, or eaches. Turning one into the other requires restaurant-specific recipe yields.

A sound worksheet also needs to separate weekdays, subtract usable on-hand prep, and account for catering, promotions, closures, and menu changes.

Example Toast CSV columns

business_date,menu_group,item_name,quantity_sold,net_sales
2026-06-01,Entrees,Chicken Bowl,38,456.00
2026-06-08,Entrees,Chicken Bowl,42,504.00
2026-06-15,Entrees,Chicken Bowl,35,420.00

Useful fields include Business Date, Menu Group, Menu Item, Quantity, and Net Sales. Quantity drives the prep conversion. Net Sales belongs in the sales review, not the prep-unit formula.

Build the conversion table

Create a maintained table with:

Menu item	Prep component	Portions per unit	Prep unit
Chicken Bowl	Cooked chicken	4	batch
Chicken Bowl	House sauce	12	quart
Roasted Vegetables	Roasted vegetables	6	pan

Then calculate:

base prep = expected menu-item quantity ÷ portions per prep unit
target prep = base prep × (1 + reviewed buffer) - usable on hand

Label the expected quantity method. A trailing three-Monday average and “last Monday” are different assumptions.

Screenshot and demo

FoodSaver column mapping screen before generating a Toast workbook

The current FoodSaver generator cleans the source exports and preserves Product Mix as a source sheet. It does not yet make prep recommendations.

Free sample workbook

The template is Excel-ready and includes formula inputs plus a review-note column for chef overrides.

Pricing

FoodSaver provides three free successful workbook generations per UTC day within free limits. Pro is $19/month or $190/year, with larger limits, saved mappings, history, email delivery, and 90-day retention.

See pricing.

Frequently asked questions

How many weeks should I average?

Start with three to six comparable weekdays. Use a shorter window after major menu, hours, pricing, or demand changes.

What buffer should I use?

There is no universal percentage. Review sell-outs, leftover prep, shelf life, batch size, and service risk. Record the chosen buffer instead of hiding it in a formula.

Should modifiers become prep items?

Only when a modifier maps to a real component and the relationship is useful. Keep modifier demand separate from base entrée quantity.

Can FoodSaver produce this automatically?

Not yet. FoodSaver currently prepares a clean workbook so the source data and exceptions are reviewable before prep logic is added.

Sources

Next: compare Toast Product Mix by day of week.

Try the free Toast Prep + OneCSV workbook generator.

How to combine Toast ItemSelectionDetails and ModifierSelectionDetails

Jun 23, 2026

Toast’s nightly data exports can include Item Selection Details and Modifier Selection Details. The files belong together, but they cannot be stacked into one table: an item row and a modifier row represent different things.

The problem

One Item Selection is a sold menu item. One Modifier Selection is a choice attached to an item. A Burger with Extra Cheese and Bacon can therefore produce one item row and two modifier rows.

If you merge by item name, check number, timestamp, or row position, repeated items can receive the wrong modifiers. If you total both tables without a documented revenue rule, paid modifier value can be counted twice.

Example Toast CSV columns

Your configured Toast export columns may differ. Preserve the originals and map the fields needed for the relationship.

Item Selection Details

item_selection_id,business_date,item_name,quantity,net_price
item-204,2026-06-22,Burger,1,10.00

Modifier Selection Details

parent_item_selection_id,modifier_name,quantity,net_price
item-204,Extra cheese,1,2.00
item-204,Bacon,1,3.00

The safe relationship is:

Modifier.parent_item_selection_id = Item.item_selection_id

Use it only when the item ID is non-empty and unique. Duplicate item selection IDs make the relationship ambiguous.

Step-by-step Excel method

Load each CSV as a separate Excel table.
Keep a source row number in both tables.
Check Item Selection IDs for blanks and duplicates.
Use Power Query to merge the modifier table into the item table with a left outer join on the exact identifiers.
Expand modifier name, quantity, and value into a detail view.
Keep unmatched modifier rows in a separate query.
Build item sales and modifier analysis as separate PivotTables.

Do not concatenate modifier names until after the row-level join has been checked. The detail table is easier to audit than one long text cell.

Screenshot and demo

Synthetic Toast Item Selection and Modifier Selection rows in the FoodSaver preview

FoodSaver follows the same exact-ID rule and puts rows that cannot be joined in the workbook’s exception view.

Free sample workbook

Open all three in Excel to practice the join with synthetic data.

Pricing

You can generate three workbooks per UTC day for free within the free limits. FoodSaverAI Pro is $19/month or $190/year and adds larger files, saved mappings, workbook history, email delivery, and 90-day retention.

Compare Free and Pro.

Frequently asked questions

Is ItemSelectionDetails the same as Product Mix?

No. Item Selection Details is row-level. Product Mix aggregates menu-item performance for a selected period.

What if a modifier has no parent item?

Keep it unmatched with its source row. Check date coverage, location, and whether the Item Selection export is complete.

Can one item have several modifiers?

Yes. A one-to-many relationship is expected.

Should I sum item and modifier net prices?

First confirm how your configured exports represent modifier charges. Keep the two totals separate until the accounting rule is documented.

Sources

Next: clean the Toast modifier report.

Try the free Toast Prep + OneCSV workbook generator.

Toast Product Mix by day of week in Excel

Jun 23, 2026

A weekday PMIX view helps answer a narrow question: what usually sells on this kind of operating day? It is more useful for prep than an all-days average, provided the date coverage is honest.

The problem

Grouping sales by weekday is easy. Building a trustworthy comparison is harder. A four-Monday sample should not be compared with five Fridays as raw totals. Closed holidays should not silently behave like zero-demand days. Refunds and report definitions also need review.

Example Toast CSV columns

business_date,menu_group,item_name,quantity_sold,net_sales
2026-06-01,Entrees,Chicken Bowl,38,456.00
2026-06-08,Entrees,Chicken Bowl,42,504.00
2026-06-15,Entrees,Chicken Bowl,35,420.00

Add helper columns in Excel:

weekday = TEXT([@business_date],"dddd")
week_start = [@business_date]-WEEKDAY([@business_date],2)+1

Use a real date value, not a text label that merely looks like a date.

Build the PivotTable

Put item_name in Rows.
Put weekday in Columns or Filters.
Put quantity_sold in Values.
Show both Sum and Average.
Add a distinct operating-date count outside the PivotTable if needed.
Divide total quantity by included open dates for a per-day average.

Keep zero sales separate from “restaurant closed” and “missing export.” Those states mean different things.

Screenshot and demo

Synthetic Toast export preview with business dates and item rows

The preview step is where you should catch mismatched locations, periods, and file types before building the weekday table.

Free sample workbook

Download the Excel-ready weekday PMIX sample and download the prep conversion template.

The sample has three Mondays so you can compare total, average, minimum, and maximum quantities without using restaurant data.

Pricing

The FoodSaver workbook generator includes three free successful generations per UTC day within free limits. Pro costs $19/month or $190/year for larger files, saved mappings, report history, email delivery, and 90-day retention.

Review pricing.

Frequently asked questions

Does Toast PMIX already show day of week?

The Toast PMIX report supports selected date ranges and day-to-day item views, but an exported analysis may still need a weekday helper column depending on the file you downloaded.

Should holidays be included?

Flag them. Include them only when the target service is comparable.

Is average enough?

No. Review sample size, range, recent trend, sell-outs, promotions, and known events. Average is a baseline, not a forecast.

Do refunds reduce PMIX quantities?

Toast documents that menu reports, including Product Mix, are not reduced by refunds. Confirm the report behavior against the operational question you are answering.

Sources

Next: turn POS sales into a prep list.

Try the free Toast Prep + OneCSV workbook generator.

Toast SFTP vs manual CSV exports

Jun 23, 2026

Manual downloads are usually the right place to prove a workflow. SFTP becomes valuable when the file set, schedule, security owner, and correction process are stable.

The problem

Teams often automate the transport before they trust the report. That replaces a visible manual task with a nightly pipeline that can quietly deliver missing, stale, or changed files.

The decision is not “modern versus old.” It is whether the recurring volume justifies key management, monitoring, retention, and re-export procedures.

Example Toast CSV columns

The transport method does not solve schema design. Whether a file is downloaded or retrieved through SFTP, confirm the configured fields:

item_selection_id,business_date,item_name,quantity,net_price
item-204,2026-06-22,Burger,1,10.00

Toast documents that automated data exports can choose the name and order of columns. That configuration can remain stable even when default web-report columns change.

Manual CSV exports

Manual downloads fit when:

the workflow is new or occasional;
a manager must adjust filters each run;
prior dates are commonly corrected;
one person can verify the file before sending it;
the downstream workbook is still changing.

The cost is repeated labor and inconsistent naming or date selection.

Nightly SFTP exports

SFTP fits when:

the same exports run every day;
a technical owner can manage SSH keys;
monitoring catches missing or late files;
access and retention are documented;
the team understands how corrected historical data is re-exported.

Toast notes that nightly export files reflect data as of export time. Alterations made later are not automatically reflected in a previously generated file; corrected dates may require manual report exports.

Question	Manual	SFTP
Setup	Low	Higher
Repeated labor	Higher	Lower
Filter flexibility	High	Configured
Key management	No	Yes
Missing-file monitoring	Human	Must be built
Historical correction	Manual by nature	Requires explicit process

Screenshot and demo

FoodSaver preview of selected Toast CSV files before processing

Regardless of transport, preview file type, date range, headers, and row counts before generating the weekly workbook.

Free sample workbook

Use the samples to stabilize the processing workflow before automating file delivery.

Pricing

The FoodSaver generator includes three free successful workbook generations per UTC day within free limits. Pro is $19/month or $190/year for larger limits, saved mappings, history, email delivery, and 90-day retention.

Compare pricing.

Frequently asked questions

Is Toast SFTP required for FoodSaver?

No. The current workflow accepts manually selected CSV files.

Does SFTP automatically fix changed data?

No. Toast states that later alterations are not reflected in an already created nightly export.

Who should own the SSH key?

A named technical or operations owner should control creation, storage, rotation, and revocation. Do not email private keys.

When should a small restaurant automate?

After the manual workflow is repeated, useful, and stable enough that failures can be recognized quickly.

Sources

Related: Toast export files explained.

Try the free Toast Prep + OneCSV workbook generator.

xtraCHEF alternative for small restaurants: when a workbook is enough

Jun 23, 2026

FoodSaver is not a feature-for-feature replacement for xtraCHEF. It is a lighter option for a narrower job: turning supported Toast CSV exports into a reviewable Excel workbook.

The problem

A small restaurant may search for an xtraCHEF alternative for very different reasons:

it needs invoice automation and inventory management;
it wants recipe costing and actual-versus-theoretical analysis;
or it simply needs cleaner Toast sales and modifier files this week.

Those are not equivalent buying decisions.

What xtraCHEF is built to do

xtraCHEF’s official product pages describe a broad restaurant back-office platform: accounts-payable automation, invoice capture, inventory, recipe and plate costing, price tracking, purchasing, and sales/PMIX analysis. Public pricing is handled through a request form at the time of this review on June 23, 2026.

Choose that class of platform when invoice and inventory workflows are the actual problem and the team will maintain the required operational data.

What a lightweight workbook workflow does

FoodSaver currently:

accepts Item Selection Details and supported optional Toast exports;
asks you to confirm columns;
joins modifiers only through exact identifiers;
creates clean item, modifier, reconciliation, and exception views;
preserves supported optional files as source sheets;
leaves accounting and operational decisions to the reviewer.

It does not scan invoices, manage inventory, calculate actual-versus- theoretical food cost, or replace accounting integrations.

Example Toast CSV columns

item_selection_id,business_date,item_name,quantity,net_price
item-204,2026-06-22,Burger,1,10.00

For the narrow workbook workflow, those item-level fields plus exact modifier parent IDs matter more than a full back-office implementation.

Decision table

Need	Better fit
AP automation and invoice coding	xtraCHEF-class platform
Inventory and recipe costing	xtraCHEF-class platform
Actual vs theoretical usage	xtraCHEF-class platform
Clean Toast item/modifier workbook	FoodSaver or a manual Excel process
One-off export cleanup	Start lightweight
Multi-location back-office standardization	Evaluate a full platform

Screenshot and demo

FoodSaver Toast workbook preview using synthetic data

View the public demo before deciding whether the narrower workflow solves enough of the problem.

Free sample workbook

Pricing

FoodSaver provides three free successful generations per UTC day within free limits. FoodSaverAI Pro is $19/month or $190/year. xtraCHEF asks visitors to request pricing; verify the current quote and included modules directly.

See FoodSaver pricing.

Frequently asked questions

Is FoodSaver a full xtraCHEF replacement?

No. FoodSaver covers a much narrower export-cleanup and workbook job.

Which option is better for invoice processing?

xtraCHEF’s documented scope includes AP automation and invoice capture. FoodSaver does not.

When should I start with a spreadsheet workflow?

When the immediate recurring pain is a small, defined file-cleanup task and you have not validated the need for a full back-office platform.

Is xtraCHEF only for Toast restaurants?

xtraCHEF says it can serve restaurants beyond Toast, while some advanced benefits are recommended with Toast.

Sources

Also compare the MarginEdge alternative decision.

Try the free Toast Prep + OneCSV workbook generator.

How to avoid double-counting Toast modifier revenue in Excel

Jun 17, 2026 - Last update: Jun 18, 2026

The Toast Prep workbook uses separate item and modifier views because the two exports answer different questions. Adding both views without a reconciliation rule can overstate sales.

Item rows record menu-item selections. Modifier rows record details attached to those selections. A workbook can count the same economic activity twice when it treats both sets of rows as independent sales.

A small numeric example

Assume the source data contains:

Source	Row	Amount
Item Selection	Burger	$10.00
Modifier Selection	Extra cheese	$2.00

A correct check total might be $12.00. A bad workbook can accidentally add the $10 item total to a separate $12 item-with-modifier total and report $22.00.

The safe review keeps the base item result and modifier detail in separate views, with a reconciliation rule that explains which values contribute to the total.

Start with item revenue

Build the base sales total from Item Selection first. This gives you one stable item-level review before modifiers enter the workbook.

At this stage, check:

total item sales;
discounts;
refunds or voids;
unusual zero or negative values;
missing menu item names;
rows outside the expected period.

Confirm how the export represents modifier values before adding them to the base total.

If you are unsure which file should provide the base grain, start with Item Selection vs Modifier Selection.

Treat modifier rows as detail first

Modifier Selection is best reviewed as detail attached to item rows.

Useful questions include:

which modifiers were selected most often;
which items receive the most modifiers;
whether modifiers are paid, included, or informational;
which modifiers cannot be matched to an item.

Those operational questions can use modifier counts and attachment detail without creating a second revenue total.

Excel and PivotTable warning

Keep item revenue and modifier detail in separate PivotTables. Use the modifier table for frequency and attachment analysis, then reconcile paid modifiers through a documented formula.

Join only by exact item selection ID

A modifier should attach to an item only when the parent item selection ID is exact and unique.

Avoid fuzzy matching by:

item name;
check number alone;
timestamp alone;
row order;
menu group.

Those fields may help a human review an exception, but they are not safe join keys for an automated workbook.

Matching method	Safe for automatic joins?	Why
Exact unique parent item selection ID	Yes	Traceable to one item row
Item name	No	The same item appears many times
Timestamp	No	Multiple selections can share a timestamp
Row order	No	Export order can change
Check number alone	No	One check contains multiple items

Keep a separate modifier detail sheet

A clean workbook can include two useful views:

an item summary with modifier information included once;
a modifier detail sheet with one row per item-modifier relationship.

The modifier detail sheet should warn reviewers not to sum it blindly with the item summary. It exists for analysis and audit, not as a second sales total.

Show unmatched modifiers

Put unmatched modifiers in an exception sheet with the source file and row number.

That gives the bookkeeper or operator a clear next step:

Check whether the source export is complete.
Confirm the date range.
Review the parent selection ID.
Decide whether the row should be included manually.

FoodSaver workbook preview showing unmatched parent IDs and voided rows in the Warnings and Exceptions tab

FoodSaver puts these rows in the workbook with their source references so the bookkeeper can resolve them before sending the report.

Frequently asked questions

Is every modifier amount already included in the item amount?

Toast report settings and exported columns can vary. Review the item and modifier amount fields before choosing a reconciliation formula.

Can I match an unmatched modifier by item name?

Use the name to investigate, not as an automatic join key. The same menu item can appear many times in one period.

What should I send to the owner?

Send the item-level summary, a short exception count, and the modifier detail needed for the question at hand. Label each table so the owner knows which figures contribute to the sales total.

Continue with the weekly Toast sales review checklist or review your exports in FoodSaver.

Weekly Toast sales review checklist for restaurant bookkeepers

Jun 17, 2026 - Last update: Jun 18, 2026

The Toast Prep workbook grew from a repeated weekly task: clean the exports, check the joins, and give the owner a short list of rows that need attention.

What sold?
Which modifiers changed the order?
Which totals need a second look?
What should the owner or general manager check next?

If you already work from Toast reports and Excel, this checklist keeps the review tight.

Download the printable weekly review checklist

1. Start with the right Toast exports

For an item-level sales review, start with Item Selection. Add Modifier Selection when you need to understand add-ons, substitutions, combos, or customizations.

Keep the original exports unchanged. Save a clean copy of the workbook you send to the owner, but keep the source files available until the review is closed.

FoodSaver Toast Prep upload step for selecting supported CSV exports

Need help choosing the files? Read Item Selection vs Modifier Selection.

2. Confirm the reporting period

Before reviewing sales, confirm that all exports cover the same dates and locations.

Check:

start and end dates;
restaurant location;
service periods;
whether voids, refunds, or comps are included;
whether the export was pulled before the POS day fully closed.

Small date mismatches can make the rest of the review look wrong.

3. Review item sales before modifiers

Item Selection is the base grain for the review. Treat each row as one item selection from the Toast export.

Look for:

high-selling items;
zero or negative values;
unusually high discounts;
voided items;
duplicate-looking rows;
missing item names or menu groups.

Do this before adding modifiers. It gives you a stable base total.

4. Join modifiers carefully

Join Modifier Selection when the item selection identifier is exact and unique. Keep unmatched modifiers visible as exceptions.

This matters because modifier rows can be easy to misread. Some reports show modifier prices. Some show context that should not be added to item revenue again.

See the numeric walkthrough in how to avoid double-counting Toast modifier revenue.

5. Keep exceptions visible

Keep messy rows available for review.

Common exceptions include:

unmatched modifiers;
duplicate source rows;
invalid or missing values;
voided selections;
rows outside the expected period;
columns that changed names between exports.

The owner needs the exception count and the questions that require a decision. The workbook can hold the row-level evidence.

Synthetic FoodSaver workbook preview with unmatched modifiers, voided items, and suggested review actions

6. Send a short owner summary

Keep the summary plain:

what files were processed;
what period they cover;
the biggest sales or modifier patterns;
exceptions that need review;
the next three checks.

Tie each statement to the source data. This export supports sales review and exception handling; prep, staffing, and purchasing need additional evidence.

Owner email template

Subject Toast sales review for [date range]

Hi [name],

I reviewed the Item Selection and Modifier Selection exports for [location].

Ready to review

[top item or sales observation]
[modifier or discount observation]

Please check

[exception category and count]
[void, duplicate, or unmatched modifier question]

The workbook includes the source references for each exception.

Thanks,
[name]

7. Save the mapping for next week

If the Toast export headers stay the same, saved mappings can save time. If the headers change, review the mapping again.

A good weekly process is repeatable:

Export files from Toast.
Confirm columns.
Generate the workbook.
Review exceptions.
Send the owner summary.

FoodSaver follows that same flow. Upload Toast exports, confirm the columns, and generate an Excel workbook with source rows, modifier joins, and exceptions ready to review.

Where FoodSaver fits

FoodSaver previews the selected CSV files, confirms the column mapping, and generates item, modifier, reconciliation, and exception views. You still confirm the reporting period, resolve accounting questions, and write the owner summary.

Frequently asked questions

How often should I run this review?

Weekly is a useful starting point for owner reporting and repeated cleanup. Month-end reviews can use the same workflow with a longer period.

Should I edit the original CSV files?

Keep the original exports unchanged. Record corrections and annotations in the review workbook so you can trace each decision.

What if Toast changes a column name?

Review the mapping again. Saved mappings should only apply to the exact same header signature.

Try Toast Prep with your files

Toast Item Selection vs Modifier Selection: what each export is for

Jun 17, 2026 - Last update: Jun 18, 2026

Building the Toast Prep workbook exposed the main reporting risk: Item Selection and Modifier Selection use different row grains. Mixing them without a clear join can distort sales and modifier totals.

Item Selection and Modifier Selection answer different questions. You need both when you want modifier detail, but Item Selection remains the base sales file.

Quick comparison

Question	Use Item Selection	Use Modifier Selection
What sold?	Yes	No
What add-ons were selected?	No	Yes
Base sales total?	Usually yes	Review before summing
Main join field	Item selection ID	Parent item selection ID
Can it stand alone?	Yes, for item-level review	Usually no

Item Selection is the base sales file

Item Selection is the item-level source for the workbook. In FoodSaver terms, one Item Selection row is one recorded sale or selection of a menu item in a Toast export.

Use it to review:

item names;
quantities;
item-level sales;
discounts;
voids;
source row numbers;
reporting-period coverage.

This is the file to start with. If you only have one Toast export, start here.

item_selection_id,item_name,quantity,net_price
item-204,Burger,1,10.00

Modifier Selection adds customization detail

Modifier Selection explains what was attached to an item. That can include add-ons, substitutions, options, and other customization choices.

Use it to review:

which modifiers were selected;
how often modifiers appear;
which item each modifier belongs to;
modifier rows that cannot be matched cleanly.

Modifier Selection needs the item-level file to make sense in a review workbook.

modifier_id,parent_item_selection_id,modifier_name,net_price
mod-501,item-204,Extra cheese,2.00
mod-502,item-204,Bacon,3.00

The two modifier rows describe the Burger selection. They are not two additional burgers.

Synthetic Modifier Selection export displayed in the FoodSaver Toast Prep demo

The join matters

The safest join is an exact parent item selection identifier. If a modifier does not have one exact, unique parent item selection, keep it in an exception sheet.

That is better than guessing.

Guessing can lead to:

modifiers attached to the wrong item;
revenue counted twice;
customization patterns that look stronger than they are;
owner summaries that are hard to audit later.

Safe join example

Item selection ID	Item	Parent ID on modifier	Modifier	Result
`item-204`	Burger	`item-204`	Extra cheese	Safe exact match
`item-204`	Burger	`item-204`	Bacon	Safe exact match
none	none	`item-999`	Avocado	Keep as an exception

Keep unmatched rows in the exception sheet. Menu name, row order, timestamp, and check number can support a manual investigation, but they make weak automatic join keys.

Why FoodSaver asks you to confirm columns

Toast exports can vary by account, location, settings, or report version. A column that appears as one header in one export may appear differently in another.

FoodSaver detects likely columns, but the review step matters. Confirming the mapping makes the workbook easier to trust and easier to repeat next week.

FoodSaver column mapping showing required Item Selection fields mapped to synthetic CSV headers

The screenshot shows the required fields used by the current workflow. Optional fields can remain unmapped when they are not present in the export.

You can also download the synthetic examples used for this guide:

A simple rule

Use Item Selection to build the base sales review. Use Modifier Selection to add detail only when each modifier can be traced back to the right item.

FoodSaver keeps that relationship visible in the generated workbook so operators and bookkeepers can review the result instead of trusting a hidden merge.

For the next step, read how to avoid double-counting modifier revenue or use the weekly Toast sales review checklist.

Frequently asked questions

Can I use Item Selection without Modifier Selection?

Yes. Item Selection is enough for an item-level workbook. Modifier Selection adds customization detail when you need it.

Should I add Item Selection and Modifier Selection totals together?

Check whether modifier values represent separate charges or detail already included in the item-level result before combining totals.

What happens when a modifier has no matching parent ID?

FoodSaver keeps it visible as an exception for manual review.

Try Toast Prep with synthetic or restaurant exports