Once you have the Master account, decide what information to share with the Child accounts before transferring the data. If you change the information afterwards, the IDs of the contents will change, and the Master account will overwrite the data in the Child accounts, causing inconsistencies.

The possible impacts are detailed below:

Employee

Employees created in the Master will synchronise with the Child accounts, which can cause:

• Changes in employee records.

  For example, if employee Carlos in the Master has ID 1 and employee Juan has ID 1 in the Child account, upon synchronisation, Carlos will overwrite Juan’s record.

• PINs that stop working or become those of another employee.

  Following the previous example, there may be employees with matching names. The employee will notice when trying to log in and the PIN either doesn’t work or shows a different name.

• Variations in reports.

  Reports showing which employee performed a certain action may display different names for previous dates after synchronisation.

App Privileges

Privileges configured in the Master will synchronise with the Child accounts. It is necessary to check that there are no differences in the synchronised privileges to prevent employees from gaining new privileges or being able to perform actions that were previously restricted.

For example, if the Waiter privilege in the Master does not allow cancelling orders, but in the Child account, it did.

Back-office Privileges

As with the app, check that the privileges synchronised in the back-office are the same as before, ensuring that employees retain their functions.

For example, the Purchasing privilege might allow employees to check inventories and access the purchasing module in the Master, but in the Child account, it only allows access to the purchasing module.

Event

When synchronising events from the Master account, ensure they are correctly configured in the Child accounts, as they will adopt the same configuration as in the Master. The only aspects not synchronised are the products and whether the event is active. These aspects can be edited from the Child account but will be lost upon resynchronisation.

For example, in the Child account, we have the Happy Hours event every Thursday and Friday from 18:00 to 20:00, whereas in the Master, it also includes Saturday. Upon synchronisation, the Child account will have Saturday enabled.

Tax Synchronisation to Catalogue

When synchronising the Master account, taxes and their configuration on products will be transferred to the Child accounts. Pay particular attention to Child accounts where the location may have its own tax regulations.

For example, if the Master account has bakery products with a tax of 4%, but the Child account is in an area where the tax is 0%, ensure these products maintain the correct tax upon synchronisation.

Tariffs

Upon synchronisation, ensure that tariffs in the Child accounts are correctly configured, active for the relevant events and products, and with the correct prices.

Keep this in mind when reviewing reports related to tariffs.

For example, if in the Master account, Coca-Cola has a terrace tariff with a different price, upon synchronisation, you must check that the Coca-Cola in the Child account has the correct price according to the Master’s tariff.

Discount

Verify in the Child accounts that discounts have been correctly overwritten upon synchronisation. If they did not match between the Master and the Child account, the Child account discounts will be lost.

Note that when reviewing reports containing discount information, if synchronisation changed the name, the reports will retain the previous name for past dates.

For example, in the Master account, there is a 10% Discount, and the accounts are synchronised today. The Child account’s reports will show the old name for past dates and 10% Discount for future dates.

Payment Method

You will not be able to activate it if the Child accounts already have generated invoices. It is important to configure it before starting to invoice with the Child accounts.

Dish Order

When synchronising, the dish orders from the Child account will be overwritten by those from the Master. Check that they are still correctly added to the relevant categories/products.

For example, if the Child account has a dish order Starters and Main Courses, but the Master only has Main Courses, upon synchronisation, Starters will disappear. Check the categories/products to ensure they have the correct order.

Printer Groups

Printer groups from the Master will overwrite those in the Child accounts if the IDs match. The printers configured in these groups will be retained, but it is important to check that they correspond to their names.

For example, if in the Child account, we have a printer group called Kitchen + Terrace with ID 4, while in the Master, ID 4 is called Kitchen + Bar. Upon synchronisation, the Child account’s group will be renamed Kitchen + Bar but will retain the kitchen and terrace printers.

Cost Price

If you have configured the cost price on products, upon synchronisation, the Master account will overwrite these prices in the Child accounts.

For example, if the cost price of a Coca-Cola is €0.75 in the Child account and €0.87 in the Master, upon synchronisation, the cost price in the Child account will become €0.87.

Supplier

Suppliers will only appear in the Master account. It is important to create all suppliers and associate them with products in the Master before synchronising with the Child accounts. If the Child accounts already have suppliers, they will be overwritten by those in the Master.

For example, if you add a beverage supplier to the Master account, upon synchronisation, the Child account will have this information in the product record.

Device Settings

Device preferences will be managed from the Master account. If they are created on the Daughter accounts, they will be overwritten by those created on the Master account.

For example, if you create a device preference for iPads on the Master account, it will be synchronised with the Child accounts.