About Us
About Equip Contact Us

Shift4 Multi-Location Deals

Last Updated: May 15, 2026

Overview

Multi-Location Management (MLM), is an optional feature set for merchants with multiple locations. It centralizes menu structures and configuration within Shift4 Dine, allowing businesses to manage menus across all locations from a single point of control.

Key clarification (from Shift4)

  • MLM is not tied to an "Enterprise" classification and is not determined by the 25 location or $25 million thresholds.
  • Any merchant can use MLM if it fits the use case.

Current Status: MLM is actively being used in approximately 300 locations across 26 concepts.

Current Capabilities

What MLM Does Today

Menu scheduling, availability, and dynamic pricing (Zendesk FAQ)

  • MLM supports menu sharing, time-based availability, and location-specific customization.
  • Menus can be scheduled by day and time using Menu Sets (for example, Breakfast, Lunch, Happy Hour, or day-of-week specials).
  • Item availability can change by menu. Turn off “Always Available” and assign items to a specific menu to control when items appear.
  • Pricing changes can be applied as:
    • Fixed values (example: +$1.00)
    • Incremental changes (example: -$0.50)
    • Percent changes (example: +10%). Percent changes round to the nearest $0.09.

Current limitations of scheduled menus (Zendesk FAQ)

  • Schedule settings apply globally and are not tied to specific locations or revenue centers.
  • Menus cannot have overlapping schedules.
  • Holiday-based menus are not supported.

Enterprise vs local behavior (Zendesk FAQ)

  • Enterprise-level edits apply to all connected locations unless a location has a local override.
  • Enterprise changes do not overwrite a location’s local version of the same item.

What locations can manage locally (when enabled)

If local creation is enabled in Enterprise settings, locations can manage their own:

  • Gratuities
  • Revenue Classes
  • Taxes
  • Surcharges
  • Discounts
  • Tenders
  • Coursing
  • Order Types
  • Modifier Sets
  • Modifiers
  • Departments
  • Items

Publishing and permissions (Zendesk FAQ)

  • Enterprise access tiers include: No Access, Partial Access, and Full Access.
  • Common permission controls include: Allow Publish, Grant User Management, Manage Users, and Manage Settings.
  • Publishing pushes Enterprise updates to connected locations. Unpublished changes remain in draft.
  • Access can be restricted by assigned locations or location groups.

Cost

  • MLM is available to multi-location merchants at no additional cost.

Partner requirements & expectations (Menu Management guidance)

đź“ŚReporting vs menu management (common confusion)

  • Shared menu editing requires the MLM console.
  • Multi-location reporting does not require MLM. Multi-location reporting can be done via Business Intelligence without shared menu management.

1) Menu standardization (required)

  • Menus across all locations must be identical (not just similar). MLM relies on exact text matching.
  • Everything must match exactly, including:
    • Item name spelling
    • Capitalization
    • Spaces
    • Modifier names
    • Modifier groups
    • Category names
    • All items must be assigned to a Department
  • If menus are not exact matches, shared management can fail and locations may behave independently.

2) First location completion requirement

  • The primary location must be fully completed and approved before adding additional locations:
    • Menu build is 100% finished
    • Merchant has reviewed and approved
    • No pending structural changes remain
  • After the first location is copied into additional locations, all future menu edits must be maintained by the partner or merchant.
  • Shift4 will not rebuild menus after locations are linked.

3) Timeline & installation expectations

  • MLM setup is a manual configuration process for the assigned Pre-Launch Specialist.
  • Expect an extended timeframe in addition to the standard 15 business days.
  • Timelines vary based on menu complexity. Changes and corrections can extend setup time.

4) Partner acknowledgement (what the partner is confirming)

  • MLM course completion (Shift4 Academy) is done prior to requesting MLM.
  • Menus are identical across all locations.
  • Primary location is complete and approved.
  • Merchant understands the manual timeline.
  • Partner will maintain the menu after linking locations.
  • Partner will handle additional merchant training once locations are added to MLM.

Recent Release Highlight (LBM 2025w51 — 12/17/25)

  • Admins can add new locations in LBM (US only), reducing support ticket dependency.
  • STMLM: Preparable Items to improve KDS routing, organization, and kitchen control.
  • STMLM: Bulk Edit Enhancements to assign taxes and modifier sets across multiple entities in one update.
  • STMLM: Discount Amount Override support when location-level overrides are enabled.
  • LBM: Table Layout Builder refreshed UI with new editing tools for better control over tables, sections, and labels.
  • Centralizes menu structures within Shift4 Dine for enterprise merchants
  • Supports central menu management with the ability to set local overrides per location
  • Streamlines configuration across multiple restaurant locations
  • Centralized printer templates and bulk edits for efficiency at scale

Key Benefits

  • Single source of truth for POS menu configuration across all locations
  • Reduced time managing menus for multi-location operators
  • Consistency across locations with flexibility for local variations
  • Scalable solution for growing restaurant groups

How control works in MLM (plain-English)

  • Menu control is centralized at the "head location" (corp level), which publishes to other locations.
  • Individual locations can still switch views and see reporting, but they cannot freely update menus.
  • The head location decides what is editable at the local level and which locations can edit it (for example, price changes only).

Current Limitations

⚠️Important: Marketplace Integration Gap (December 2025)

MLM centralizes menu structures within Shift4 Dine only. It does not yet extend to Marketplace online ordering menus (e.g., DoorDash, Uber Eats, Grubhub).

What this means for merchants today:

  • Menu updates for Marketplace integrations still need to be done per location
  • Merchants must manage menus in two places: Shift4 Dine (via LBM) and Online Menus (via Marketplace Menu Manager)
  • No single source of truth across Shift4 Dine and third-party delivery platforms yet 

What's Coming: Unified Menu Management

The Marketplace team is actively working on a unified menu management solution built off MLM.

Future Vision

Once complete:

  • MLM will serve as the single source of truth for all menus
  • Marketplace integrations (DoorDash, Uber Eats, etc.) will consume the same centralized menu from MLM
  • Eliminates the need to manage multiple menu copies across different systems
  • One update in MLM will propagate to both Shift4 Dine and all online ordering platforms

Timeline: Development is slated to start in the new year (2026).

Bottom Line for Merchants

âś… Today: MLM centralizes menus in Shift4 Dine, but not Marketplace yet

âś… Coming Soon: Unified menu management is planned and in development

⏳ For now: Merchants with Marketplace integrations must continue managing menus separately in:

  • LBM (Lighthouse Business Manager) for Shift4 Dine menu configuration
  • Marketplace Menu Manager for online ordering menus

Related Resources

  • For menu programming questions: Contact your Pre-Launch Specialist
  • For technical support: Shift4 Support
  • For Marketplace Menu Manager questions: Contact Marketplace support team

Rep Guide: Shift4 Dine’s Multi-Location Manager (MLM)

What this is

Shift4 Dine's Multi-Location Manager (MLM) is an optional Shift4 Dine feature set designed for merchants with multiple locations. It helps centralize and standardize configuration across locations, but it has a different setup flow than single-location deals.

When this matters

Use this guide when a deal involves:

  • Two or more locations under the same owner.
  • A need to coordinate installs and menu build across multiple sites.
  • A merchant who expects centralized menu and configuration control.

Is STMLM the right fit? Key evaluation questions

Best-fit vs poor-fit (quick filter)

  • Best candidates: Multi-location owners who want a high degree of centralized control and have nearly identical menus across locations.
  • Not good candidates: Multi-location owners whose locations operate independently or have meaningfully different menus.

If a merchant is multi-location but not MLM

  • Merchants can still be multi-location without MLM. In that setup, they can switch between locations in the top left, and Lighthouse looks the same for every location.

🔍Source: Daniel Fite — Shift4 Partner Manager guidance (January 2026)

When evaluating STMLM for use with your merchants, consider these important questions to determine fit:

 

  1. How many locations does the merchant have?

Merchants with only 2 locations might not be the best fit for an enterprise menu management product. You are adding complexity and centralized management to a small organization that might not realize time savings and will sacrifice some simplicity.

  1. How similar are the menus at the locations?

Merchants should be using a very common menu across their sites to benefit from centralized menu management.

  • Example of poor fit: If 40 food items are the same but the specials, drinks, beer, wine and liquor are all unique to each site (meaning 90% of your menu has to be managed at the site level and not through the corp database), this merchant is not a good fit.
  • The benefit: Centralized management comes from accepting that benefit over the risk of allowing the site management to create menus and prices. Ensure your merchant considers the setup of the menus and the complexity added to the environment before the request for STMLM.
  1. Is the merchant looking to manage most of their items from a corporate database with hands off from their onsite management?

Talk about the power of centralized menu management, the removal of the control of pricing from the sites and the scheduling of menu rollouts from the Corp level database.

  • STMLM is not a substitute for simply copying a menu from one site to use at another site as a base dataset.
  • It is a full menu management suite that creates a corp level database.
  • STMLM does not prevent local menu management. Specials, unique beer lists, etc. can be added and maintained at the site level.
  1. Is your site prepared to do one installation, get the menu and modifiers completed and approved, then move on to creating their corp level database for push to subsequent locations?

This is what a rollout at STMLM should look like. Starting with a clean well tested dataset and pulling it to corp level will greatly improve the satisfaction of the merchant and give them time to explore before the whole STMLM environment is live.

  1. Does site 2-100x have an empty MID with no menu?

Sites with current menus cannot receive a corp level menu. STMLM cannot merge items coming from corp level with items that already exist at the site.

  • It is "possible" to create one from many but the merchant needs to prepare themselves to manually merge items into one location for preparation of creating the corp level data and then new MIDs will need to be created.
  • Merchants that are willing and able to fully participate and create what is needed for the Corp level database can transition to STMLM with dedication and labor hours.

đź’ˇIn summary: No one wants to pair a merchant with a solution that is more than what they need or adds unneeded complications to their environment. STMLM is an amazing product and does MLM in a very user friendly manner. It's simple and well designed if the merchant you are solving with STMLM, ensure its a good fit, and then help them through the launch. Merchants that find success with MLM are likely to be long time profitable merchants.

If you have questions on STMLM, please reach out to your Partner Manager for more information.

Key rep reminders

  • Use a unique "merchant name" per location. This is the location label used in Lighthouse/Shift4 for each site (not the owner's name). Example: "Burger Bob's - Murfreesboro" and "Burger Bob's - Tiptonville."
  • Ensure the PLS team knows all locations are under the same owner.
  • Coordinate install dates strategically.
  • When submitting orders for additional locations (2nd, 3rd, 4th, etc.), add a heads up in the onboarding form email so the order routes to the same PLS as prior locations.

Critical timing for MLM decisions

  • It is easy to add or remove MLM early in onboarding, before programming and deployment.
  • Once a merchant is programmed, installed, and live, removing MLM is very difficult.
  • If an order comes in tagged as MLM, PLS will confirm the merchant understands what MLM changes.

Ordering MLM in Sales Center (required steps)

When placing an order in Sales Center for a merchant that requires MLM, follow the guidance here.

  • Academy course (required). Completion is required before requesting MLM.
    • Partner Portal → Learning → Enter Shift4 Academy → My Learning → find Shift4 Dine Multi-Location Management.
    • If it is not listed, click Catalog and search, then enroll and return to My Learning.
  • Sales Center selection. Select Multi-Location Management in Sales Center when placing the order.
  • Shift4 programming required. Orders with MLM must have Shift4 programming selected.
    • This applies to every MID using MLM, even if the change is only linking an additional site.
  • Merchant fit check. Confirm the merchant’s needs match the intention of MLM.
    • Important: Once a menu is moved to MLM, it cannot be reverted back to individual menus.

Known limitations and common friction points

  • Item routing cannot be edited in Lighthouse. Routing changes must be made on-site.
  • If an item is added to all locations, each site must be routed manually.
  • KDS “preparable” item settings may not be available in some MLM scenarios.
  • No bulk edits for items in some workflows.
  • Course assignment can be item-by-item.
  • Order type colors may not be set (and may not display correctly in Shift4 Dine Mobile App).
  • Shift4 Dine Mobile App metrics may appear tripled (noted as a possible MLM glitch).
  • Support gaps: some support reps may not be familiar with MLM or may lack access.

Helpful references

  • Shift4 Dine Multi-Location Management (Shift4 Zendesk)
  • Multi Location Features in Lighthouse Business Manager (Shift4 Zendesk)

âś…If you are unsure whether MLM applies to a deal, route the question to the Pipeline Manager before promising any specific workflow or timeline.

Â