​

SIDES POS

Use the SIDES POS integration to connect your SIDES restaurant management system with Mathership. The integration syncs SIDES stores and products, lets you map products to ingredients or recipes, and creates inventory ledger entries from SIDES sales data.

​

What the integration can do

The integration can:

• Connect SIDES using username and password credentials
• Test the SIDES connection at any time
• Update credentials without losing setup data
• Sync SIDES stores
• Sync SIDES products
• Link SIDES stores to Mathership storage units
• Map SIDES products to ingredients or recipes
• Run a 90-day historical migration
• Run automatic daily transfers
• Run manual one-day transfers
• Create inventory ledger entries from SIDES sales
• Keep transfer logs for review and troubleshooting

​

What the integration does

When a SIDES transfer runs, Mathership:

1. Fetches SIDES sales data for one store and one date
2. Stores the raw SIDES orders and bill positions
3. Reads the sold product names and quantities
4. Finds matching POS mappings in Mathership
5. Deducts mapped ingredients directly
6. Expands mapped recipes into recipe ingredients
7. Calculates inventory quantities
8. Creates inventory ledger entries
9. Stores a transfer log with statistics, errors, skipped lines, and unmapped items

​

What the integration does not do

The SIDES integration does not:

• Create ingredients automatically
• Create recipes automatically
• Guess product mappings automatically
• Deduct inventory for unmapped products
• Optimize stock levels
• Change SIDES sales data
• Push inventory back to SIDES
• Create purchase orders
• Calculate delivery routes

​

Recommended setup order

Use this order for a clean SIDES setup:

​

Before you start

Before connecting SIDES, prepare these Mathership inventory objects.

​

Storage units

Each SIDES store must be linked to one Mathership storage unit. The storage unit defines where inventory should be deducted.

​

Ingredients and recipes

Ingredients are the inventory objects that are deducted. Use recipes when one sold SIDES product consists of several ingredients. When the SIDES product is sold, Mathership deducts the ingredients inside the recipe.

​

Connect SIDES

Use the connection form to connect Mathership with SIDES.

​

Connection form fields

​

Test the connection

After connecting, test that Mathership can reach the SIDES API: Use Test connection whenever you suspect credentials have changed or the connection has broken.

​

Edit credentials

You can update credentials at any time without losing stores, products, mappings, or transfer history. Leave the username or password field blank to keep the current value.

​

Manage stores and products

From the integration panel, use the two navigation buttons:

• Manage stores — opens the store list for this integration
• Manage products — opens the product list for this integration

​

Sync stores

Sync stores to import the SIDES stores available to your account.

​

Store list columns

​

Store list filters

Filter the list using the toolbar chips:

​

Link a storage unit

Each SIDES store must be linked to a Mathership storage unit before it can be activated or process issues. The same sold product can deduct inventory from different storage units depending on the store.

​

Sync products

Sync products to import SIDES products into Mathership.

​

Product list columns

​

Product list filters

​

SIDES product types

​

Map SIDES products

Click any product row to open the mapping sheet. Each SIDES product must be mapped before it can create inventory movements. You can map a product to:

• An ingredient — the ingredient is deducted directly per sale
• A recipe — the recipe is expanded into its ingredients and all lines are deducted

​

Why mapping is required

Without a mapping, Mathership can store the sale but cannot create the correct inventory deduction. When a recipe is sold, Mathership expands all recipe lines including nested child recipes and deducts each ingredient.

​

Mapping fields

​

Mapping examples

​

Activate a store

A SIDES store must be activated before migration and regular transfer processing can run. Before activation, make sure:

• The store has a storage unit
• Important SIDES products are mapped
• Recipes and ingredients are set up correctly
• You understand which storage unit will receive the deductions

​

Store detail page

Opening a store shows a live overview of its status, health, activity, and configuration.

​

Store metadata

The detail page header shows the store name, activated badge, auto issue badge, and any of the following status badges when applicable:

​

Health indicators

If any of the following are detected, a warning banner appears at the top of the page:

• No storage unit linked
• Store is marked as coming soon
• Store is temporarily closed
• A migration is currently in progress

​

Stats

​

Configuration

​

90-day migration

When a store is activated, Mathership creates a 90-day historical migration that processes past SIDES sales and creates inventory movements where mappings exist.

​

Migration date range

The default migration range is the last 90 completed days, ending yesterday.

​

Migration statuses

​

Migration progress fields

​

Migration actions

​

Automatic transfer

Toggle Auto issue in the Configuration section to pause or resume automatic daily processing. Pause automatic transfer when:

• Mappings are incomplete or being corrected
• A storage unit link is wrong
• You are investigating unexpected inventory movements
• You want to prevent automatic deductions temporarily

​

Manual transfer

Use manual transfer when you want to process one specific day. Manual transfer is useful for:

• Testing the integration before enabling automatic transfer
• Reprocessing a day after mapping changes
• Fixing inventory after a failed transfer
• Checking a specific SIDES sales date

​

What happens during transfer

When a SIDES transfer runs, Mathership:

1. Checks that the store has a storage unit
2. Creates a transfer log
3. Fetches SIDES sales data for the selected date
4. Stores SIDES orders and bill positions
5. Reads sold product names and quantities
6. Skips lines already posted to the current storage unit
7. Matches sold product names to POS mappings
8. Deducts mapped ingredients directly
9. Expands mapped recipes into ingredients
10. Calculates weighted average cost
11. Creates inventory ledger entries
12. Links ledger entries to SIDES bill positions
13. Updates the integration last run time
14. Saves transfer statistics and errors

​

Sales line processing

Only positive bill positions with a product name are processed. A bill position is skipped when:

• Quantity is missing, zero, or negative
• Product name is missing
• The line was already posted
• The product is unmapped
• The mapped ingredient or recipe cannot be resolved

​

POS mapping match

The transfer matches SIDES bill positions to POS mappings by product name. The SIDES product name must exactly match the mapped POS product name.

​

Transfer result

The last successful issue section on the store detail page shows:

​

Transfer statistics

Detailed transfer statistics stored in the log can include:

​

Unmapped products

If a sold SIDES product has no mapping, Mathership records the product name as unmapped and does not create any inventory deduction.

​

Processing logic

​

Ingredient mapping

If the mapping points to an ingredient, Mathership deducts that ingredient directly.

​

Recipe mapping

If the mapping points to a recipe, Mathership explodes the recipe and deducts all recipe ingredients. Recipes can contain child recipes. If a mapped recipe contains a child recipe, Mathership expands it as part of the transfer. Recipe lines can include a trim percentage. If trim percentage is invalid, the transfer records an invalid_trim_pct exception. If recipes reference each other in a cycle, Mathership stops the expansion and records a recipe_cycle exception.

​

Weighted average cost

Mathership calculates unit cost from receipt ledger entries using: total receipt value / total receipt quantity If no receipt quantity is available, the unit cost is 0.

​

Inventory ledger entries

Each inventory ledger entry is linked to:

• Company and ingredient
• Storage unit
• Quantity deducted
• Unit cost and total value
• Date
• SIDES store
• Transfer log
• SIDES bill position

See Ledger for detailed inventory history.

​

Transfer logs

Each issue attempt creates a transfer log. Open logs from the See all logs button on the store detail page. The store detail page also shows the last 10 failed transfers directly, including report date, attempt number, start time, and error message.

​

Testing checklist

Before relying on automatic transfers, test one day manually and check that:

• The correct SIDES store was used
• The store has the correct storage unit
• The correct date was processed
• Sold products were found
• Important products are mapped
• Recipe ingredients were deducted correctly
• Quantities are correct
• Ledger entries appear in the correct storage unit
• Unmapped product names are expected
• Transfer log status is successful
• No unexpected exceptions appear

​

Best practices

​

Common problems

​

Related pages