Import-led switching

See your menu in MarginKind before you move service

Toast and Square imports are already shipped in the product. The switcher story starts with a staged import, AI-assisted recipe drafts, and manager review before anything becomes operational.

Try the import demo Compare platforms

Flow

From export to reviewed operating data

Step 1 - shipped

Export from Toast or Square

Bring a current menu export into a staging tenant so managers can review structure before the service team depends on it.

Step 2 - shipped

Map items and modifiers

Imported rows are mapped into MarginKind menu and product records, with conflict decisions kept visible for review.

Step 3 - shipped

Queue AI recipe drafts

Menu items marked for generation can queue AI-assisted recipe drafts, then fall back safely when a live model is unavailable.

Step 4 - shipped

Review and commit

Managers inspect recipes, ingredients, allergens, and source confidence before committing operational data.

Demo screenshots

Screens captured from the existing demo screenshot workflow

Menu hub screenshot from the demo dataset — Menu review uses the same demo screenshot pipeline as module pages.

Recipe context screenshot from the demo dataset — Recipe context remains reviewable before managers commit changes.

Inventory cost accountability screenshot from the demo dataset — Imported menu decisions flow into stock and cost review.

Demo clip

Captioned import review walkthrough

The silent WebM loop is generated from the demo screenshot pipeline and keeps the poster fallback for slower connections.

Import review

Captioned silent loop generated from the import and AI recipe review demo screenshots.

Why this is the switcher centerpiece

Operators do not just need another demo account. They need proof that their menu, recipes, and stock assumptions can be inspected before a cutover. Import-led migration turns the highest-risk switching question into a review workflow.

Plan an import walkthrough