Importing Staff

Applies toStarter plan and up Needs Store Settings · ImportUsually owner, manager

You can import staff members into Fuze Store POS to set up or update your team in bulk. This is useful when onboarding multiple employees or migrating from another system.

The Import Staff dialog in the Fuze Store app showing a CSV file upload area and a Download Template button — Import → upload a file

Step-by-Step Guide

Open the app drawer.
Go to Configurations.
Under Data Management, tap Import.
Choose the matching data type on the type grid.
Optionally tap Download template for a CSV starter (your live export).
Upload a CSV, XLS, or XLSX file, review the preview, then confirm Import.

Before you import

Staff limit. New rows with an email are invitations and count toward your plan's staff limit, the same as adding staff one by one. Rows without an email are POS-only staff and never count. If the file would go over the limit, nothing is imported.
Roles you can give. You can only give a role whose permissions you have yourself. The store owner and organization admins can give any role. If one row asks for a role you cannot give, nothing is imported.
Roles that never change. The import never changes the owner's role or your own role. The role_id on those rows is ignored.

Field Reference

Here are the columns in the Staff import file:

Field	Description	Required	Example
id	UUID identifier for the staff member. Leave empty to create a new entry.		123e4567-e89b-12d3-a456-426614174000
role_id	UUID or code identifier of the role to assign.		123e4567-e89b-12d3-a456-426614174001 or barista
first_name	First name of the staff member.	Yes	John
last_name	Last name of the staff member.	Yes	Doe
email	Email address of the staff member.		john.doe@email.com

Pay Structure Columns

If your store has the Staff Pay add-on, the file also has five pay columns, the same fields as the Pay structure and Default commission rate sections of the staff form. You see them only if you're allowed to view staff commissions, and they're imported only if you're allowed to manage them. Otherwise they're ignored.

Field	Description	Required	Possible Values	Example
pay_type	How the staff member is paid.		COMMISSION_ONLY, FIXED_ONLY, FIXED_PLUS_COMMISSION, GREATER_OF, OTHER	FIXED_PLUS_COMMISSION
base_pay_amount	Base pay per unit.	With FIXED_ONLY, FIXED_PLUS_COMMISSION or GREATER_OF	A number from 0 to 99,999,999.99	500
base_pay_unit	How the base pay is counted.	With FIXED_ONLY, FIXED_PLUS_COMMISSION or GREATER_OF	MONTHLY, WEEKLY, DAILY	DAILY
commission_rate_type	The staff member's default commission rate type.	With commission_rate_value	PERCENT, AMOUNT	PERCENT
commission_rate_value	The default commission rate.	With commission_rate_type	A number with up to 2 decimals: 0–100 for PERCENT, 0–999.99 for AMOUNT	12.5

A blank cell keeps the saved value. An older file without these columns imports without touching anyone's pay.
New staff with blank pay cells start as COMMISSION_ONLY with no default rate, the same as the form.
Switching someone to COMMISSION_ONLY or OTHER clears their base pay. Base pay filled in for a staff member whose pay type has none is ignored.
Values aren't case-sensitive: fixed_only works as well as FIXED_ONLY.
Enter plain numbers: no currency sign, thousands separator or % (1000, not ₱1,000; 10, not 10%).

See Staff Pay Structure for what each pay type means.

Tips

Review your data before importing to avoid errors.
Download a sample export file first if you are unsure about formatting.
Make sure each staff member has the correct role assigned.
Keep staff records up to date as your team changes.

Edge cases

All or nothing. Every row is checked before anything is saved. One bad row stops the whole import and nothing is saved. The app lists each problem as Row 2: … and names the column.
How a row is matched. A row matches an existing record by its id first, then by its email. A row that matches is updated, and every other row is added. A row with none of these is always added, so running a hand-made file twice makes duplicates. Export first and edit that file to update safely.
Spreadsheet formats. You can upload .csv, .xls, or .xlsx. The file is read by what it really is, so a damaged or unreadable spreadsheet is refused as a bad format. A CSV with a single column has no separators and is refused as not being a spreadsheet, so add a second column or save it as .xlsx.
Headers matter, not order. Extra columns are ignored. YES/NO and other fixed values accept any letter case, and blank cells fall back to the default for that column.
Starter and up. Import is not on the free Basic plan. It needs Store Settings · Import, and Download template also needs Store Settings · Export.
Staff limit. New rows with an email count toward your plan's staff limit (Basic 3, Starter 5, Lite 10, Standard 15, Premium none). Rows without an email never count.
Roles first. If you use custom roles, import them before staff. You can only give roles within your own permissions.
Pay fields. Switching someone to COMMISSION_ONLY or OTHER clears their base pay. Base pay for a pay type that has none is ignored. Enter plain numbers, with no currency sign, separator, or %.

Works with

Add-on or plan	What changes
Basic plan	Import and export are locked.
Staff Pay add-on	Pay types and commissions apply when it is active. See Staff Pay Structure.
Roles & Permissions add-on	Custom roles must exist before staff reference them.