Stores And Teams

Stores are the central operational unit in Tapidu.

Store Directory

Use the store directory to search, filter, and review store condition before opening a specific store. Useful filters include lifecycle status, TapiCube condition, activity, and attention state.

For single-store owners or managers, the admin can route directly to My store instead of showing a directory that adds no value.

Store Info

Store profiles can include address, phone, email, logo, lifecycle state, commerce integration setup details, and QR scanner settings.

Recommended store profile fields:

• public store name
• internal store code
• address
• contact email and phone
• logo
• QR scanner mode settings
• Commerce integration settings for WooCommerce and Shopify

Keep store codes stable once integrations and TapiCubes are configured.

Store Lifecycle

Platform admins can mark a store active, suspended, or closed. Lifecycle changes are logged and can trigger notifications.

Lifecycle states should be used deliberately:

• Active: normal operation.
• Suspended: temporarily blocked while preserving history and access context.
• Closed: no longer operating, but retained for historical reporting.

Team Access

Use the Team section to invite staff, promote existing app users, assign stores, and deactivate access. Platform admins see the full team directory. Store owners and managers see only their permitted store scope.

Team changes should be reviewed carefully because access controls affect customer data, point adjustments, rewards, checkout claims, notifications, and scanner mode.

Team Directory And Invites

The Team area is split into:

• Directory: search, filter, and edit existing members.
• Invite member: add a new team member or promote an existing app user.

Platform admins can manage platform admins, owners, managers, and staff. Store owners and managers should only manage roles permitted for their stores.

Notices

Store owners and managers can post store notices. Platform admins can post platform-wide notices or store-specific notices. Each notice keeps author and resolution information.

Use notices for temporary operational context, such as:

• holiday opening changes
• known device issues
• campaign instructions
• staff reminders
• platform warnings

Resolve notices when they are no longer relevant so the Overview remains focused.