Orpinn • Multiple branch operations

Share branch catalogs while keeping branch activity attributable

Orpinn organizes an account into organizations and branches, with shared catalog and configurable price and image sharing under enabled services. Define common data and user access while keeping stock quantities, sales, purchasing and accounts associated with each branch. Available controls depend on product, version and synchronization entitlement.

What does the organization manage across branches?

Managing a restaurant or retail chain starts with clear decisions: is the menu shared, are prices shared, who edits products and who can access each branch? Configure sharing and permissions around those questions while retaining the context of each daily transaction.

Organizations and branches

Group business branches in an account organization and assign authorized user access. Clear branch records connect catalogs, services and licenses to the correct business context.

Shared catalog

Shared catalog setup organizes products, categories and choices across organization members. When connecting existing catalogs, review merging or using a selected source catalog and understand the effect before applying the decision.

Price and image sharing

You may need a common product list with equal prices or different pricing between locations. Organization settings determine price and image sharing rather than assuming every branch field must be copied.

Authorized remote management

The client portal and remote management provide enabled data and actions within authorized branches. Access follows user permissions and service entitlement so management views reflect the responsibilities assigned to each person.

Branch reporting and activity

Review sales, stock and accounts in their branch context. Sharing a product name or image does not turn stock or cash into one shared balance; activity retains its branch and operational source.

Synchronization and device configuration

Review product, version, device connections and enabled services before configuring sharing. Setup explains which records synchronize, which operations require connectivity and which data remain local to a branch.

How do you configure a multi-branch organization?

  1. 1

    Inventory current catalogs

    List branches, products, barcodes, prices and images and identify the intended catalog source. Review differences before choosing sharing or replacement.

  2. 2

    Configure sharing and access

    Define shared records, editing responsibilities and each user branch access. Review synchronization entitlement and required versions during setup.

  3. 3

    Verify the branch workflow

    Check product updates in the intended branches and verify separate quantities and accounts. Review the workflow on the actual devices before relying on operation.

Branch and synchronization questions

Can products be shared with different branch prices?

Organization settings define catalog, price and image sharing under the enabled product and service. Review the intended pricing policy during setup to align each branch with how you sell.

Does sharing products combine branch inventory?

No. Sharing a product definition does not combine its quantities, sales or branch accounts. Inventory and movement retain their branch and warehouse context.

What is needed to join a branch with an existing catalog?

Review the branch and organization catalogs, the intended source and the merge or replacement controls available in the installed version. Understand the resulting catalog before confirmation.

Does every synchronization operation work offline?

Internet synchronization needs connectivity to the service. Branch and paired-device operations have connection requirements depending on product and setup; these are reviewed during equipment configuration.

Prepare a proposal for your business

Share branch counts, product and version, catalog size and the required sharing of products, prices, images and user access. We review service entitlement and explain joining and detachment behavior before configuration.

Discuss your branch setup