Menu & Catalogue
Understand the MiniTill menu structure
Learn how the shared business catalogue, store settings, POS, online ordering, and marketplace menus fit together.
Overview
- MiniTill uses one core Business catalogue for categories, products, modifier groups, and modifier options. Stores do not need separate copies of the same menu.
- The Business catalogue defines what an item is: its name, base price, category, description, tax treatment, modifier groups, images, and default visibility.
- Each Store then controls how that catalogue is used locally, including store-specific prices, visibility, availability, marketplace pricing, POS layout, and other store-level settings.
- The same catalogue can feed POS, MiniTill Online Ordering, and supported marketplace publishing. This avoids rebuilding the same menu independently for each channel.
When to use this
- Read this before creating a menu, especially if you have more than one store or sell through more than one channel.
- Use this structure to decide whether a change belongs at Business level or Store level.
Step-by-step
- Create Business-level Categories, Modifier Groups, and Products.
- Assign each product to a category and link the modifier groups that customers or staff should choose from.
- Set default POS/online visibility and a base price on the product.
- For each Store, review local product visibility, store price overrides, marketplace prices, and current availability.
- Arrange products in POS Layouts for fast counter entry.
- When Online Ordering or a supported marketplace is enabled, review the channel-specific presentation and pricing rather than creating duplicate products.
Common mistakes
- Do not duplicate the same product just because two stores charge different prices; use store price overrides.
- Do not create a second product just to charge a different marketplace price; use marketplace pricing.
- Do not delete and recreate a product merely because it is temporarily unavailable; use availability controls.
- Do not assume changing a Business-level default will always overwrite an existing Store override.
Troubleshooting
- If a product exists but cannot be sold in one store, check the Store-level enablement/visibility and availability.
- If a price looks different between POS and a marketplace order, review base, store, and marketplace price overrides.
- If an item appears online but not on POS, compare the separate POS and Online visibility settings.
- If a product is difficult for staff to find on POS, check the POS Layout rather than changing catalogue order alone.