Cubigo

Cubigo syncs Apicbase recipes and menus with resident ordering and imports sales automatically. This article explains how to set up the connection, what to expect, and how to resolve common issues.

Table of Contents

1. How to connect to Cubigo

2. What to expect

3. Data behaviour and limitations

4. Troubleshooting

5. Onboarding

6. Contact information

1. How to connect to Cubigo

Prerequisites

Before Cubigo can fetch or send data, several custom fields must be created and correctly configured in Apicbase. You must have all required custom fields set up, create all recipes and products in Apicbase before creating them in Cubigo, and ensure API access is active in both systems. If custom fields are missing, Cubigo cannot retrieve recipes or menus from Apicbase.

Activating the integration in Apicbase

1. Go to Outlet Settings → Integrations.

2. Select Cubigo in the Point of Sales Integration dropdown.

3. Save the configuration.

Selecting the region and Location ID

Select the correct region (US, EU, or UAT – Testing). Leave the Location ID empty, as Cubigo already includes the correct location ID in the sales data.

When to use a Location ID:
Only if Cubigo has additional locations that Apicbase does not yet recognise (rare scenario).

2. What to expect

Data flow Apicbase → Cubigo

Cubigo fetches recipes and menu data.

Data flow Cubigo → Apicbase

Apicbase imports the sales item name, the Apic ID (PLU), and the quantity, timestamp, and location.

Because Cubigo generates items from Apic IDs, Apicbase recognises them automatically.

Product linking and PLU logic

Items created in Apicbase first appear with a PLU and link automatically.
Items without a PLU were created in Cubigo before they existed in Apicbase, which should not occur.

Modifier rules

Modifiers must exist as separate recipes or products in Apicbase.
Cubigo can only fetch them if the Apic ID is set up correctly.
Modifiers cannot create new IDs; they must reference existing Apicbase items.
If modifiers do not appear, check custom fields, menu assignment, or missing IDs

3. Data behaviour and limitations

Apicbase does not send stock levels or inventory movements to Cubigo. Cubigo does not return menu structures to Apicbase. Sales sync only if orders are marked as Delivered i Cubigo. Auto-linking works only for items with valid Apic IDs.

4. Troubleshooting

Missing sales (not marked “Delivered”)

If sales from yesterday do not appear in Apicbase:

Orders not marked as Delivered before the nightly sync.
Fix: Mark the orders as Delivered in Cubigo, then trigger a manual sync in Apicbase or wait for the next scheduled import. 

Missing or incorrect custom fields:

Cubigo cannot fetch menus or recipes, items may appear incomplete, and sales may not be recognised.

Fix: Ensure all required custom fields match the technical setup. Contact your CSM if fields must be added.

Products appear without PLU

Items were created in Cubigo before they existed in Apicbase.
Fix: Create the recipe in Apicbase, update the Cubigo item so it uses the correct Apic ID, and reimport the sales if needed.

Sales or items do not come through

Check:

• Were recipes created first in Apicbase?

• Are custom fields missing?

• Was the item renamed in Cubigo?

• Did someone create an item in Cubigo manually (no Apic ID)?

• Is the wrong region selected in Apicbase?

5. Onboarding

To activate the integration:

1. Complete the technical configuration.

2. Contact your Apicbase Customer Success Manager to enable Cubigo for your organisation.

3. Configure the correct region per outlet.

4. Validate product linking.

5. Run a test sales import.

6. Contact information

For setup issues, missing fields, data not syncing:
Contact your Apicbase Customer Success Manager.

For Cubigo-specific questions (order status, menus, settings):
Contact your Cubigo support representative.