Skip to main content

Organization, Tax, and Loyalty

Organization pages combine information shared by every location with one store-specific tax view. Confirm the organization in the sidebar before making changes. On Store Tax Policy, also confirm the selected store.

Page and scope reference

Navigation labelScopeAccess neededFeature needed
OverviewOrganizationorg.members.readpeakpos.organization
OrganizationOrganizationaccount.organization.readpeakpos.organization
LocationsOrganization listorg.members.readpeakpos.organization
StaffOrganizationboth org.admin and org.members.readpeakpos.staff
CategoriesOrganizationorg.categories.readpeakpos.catalog
SuppliersOrganizationorg.suppliers.readpeakpos.catalog
TaxOrganization/storetax.configuration.read or store.tax.readworkspace.tax
Store Tax PolicySelected storestore.tax.readworkspace.tax
JurisdictionsOrganizationtax.configuration.readworkspace.tax
ExemptionsOrganizationtax.configuration.readworkspace.tax
Audit LogOrganizationreporting.reports.readworkspace.reporting
Loyalty ProgramOrganizationorg.loyalty.writeworkspace.loyalty
Loyalty AnalyticsOrganizationorg.analytics.readworkspace.loyalty

A page appears only when its listed PeakPOS feature is enabled for the organization. A visible page can still show read-only or fewer controls when you do not have the additional task permission described below.

Review the organization Overview

Go to Organization > Overview to see a rollup across locations:

  • Locations, Total Staff, Org Revenue, and Org Members
  • The current Subscription Tier, when available
  • Sales by Location and Location Summary
  • Recent activity for the currently selected store

Use Refresh to request current data. The updated indicator confirms when the most recent refresh completed. Contact Peak Support to change organization settings or organization access; this page is a summary, not an editor.

Go to Organization > Organization to review the record used on invoices and receipts.

  1. Under Profile, verify Legal name, Default currency, EIN, Tax ID, Email, Phone, and Website.
  2. Under Legal/billing locations, verify the primary and other bill-from addresses.
  3. To edit a POS store's operational phone number, use Locations instead.
  4. To change the legal profile, legal/billing locations, or any other POS store details, contact Peak Support.

Legal/billing locations are different from POS store locations. Do not use a store-location edit to try to change the bill-from identity on an invoice or receipt.

Review and edit Locations

  1. Go to Organization > Locations.
  2. Review each location's Name, Address, Phone, Hours, and Active status.
  3. Select a row to open Store Details.
  4. If you have store.settings.write, select Edit to update the phone number, then select Save.
  5. Wallet coordinates are generated automatically from the store address when a customer first adds a wallet pass. No merchant action is required.

Phone edits affect the store's POS, receipts, and contact details. Adding or removing a location, and changing its name, address, hours, active state, or invoice bill-from address, are Peak Support tasks.

Manage organization Staff

Go to Organization > Staff to review organization members and pending invitations.

  • Staff lists the organization roster and effective roles.
  • Pending Invites lists invitations that have not been accepted.
  • Users with org.invites.write can select Invite Organization Staff, choose an email and Organization Role, and send the invitation.
  • The same permission enables Import CSV for bulk invitations and Cancel invite for a pending invitation.

Assign only the role needed for the person's work. Store membership and store roles are managed separately from the organization roster.

Maintain Categories

Categories are one organization-wide product taxonomy shared by every store.

  1. Go to Organization > Categories.
  2. Review category names, hierarchy, active state, and sort order.
  3. Users with both org.admin and org.categories.write can select Add Category.
  4. Enter Name, optionally choose a Parent category, set Sort order, and save.
  5. Use Edit to change a category or make it inactive without removing its history.
  6. Use Merge when products should be reassigned into another category. Review the destination before confirming.
  7. Use Import CSV for a validated bulk change; download and follow the provided template.

Delete is available only when the category has no blocking dependencies. Prefer deactivation or a deliberate merge when historical catalog and reporting continuity matters.

Maintain Suppliers

Suppliers are also organization-wide. Their product links provide the preferred supplier used by low-stock reorder drafts.

  1. Go to Organization > Suppliers.
  2. Select a supplier to review contact information, payment terms, and Product purchasing links.
  3. Users with both org.admin and org.suppliers.write can select New Organization Supplier.
  4. Enter Name and, as available, email, phone, address, and Payment terms.
  5. Open a supplier to edit it or to add and remove product purchasing links. Before adding a link, select the store whose catalog contains the product; then choose the product, optionally enter Supplier SKU and Cost, choose whether it is the Default, and select Link.
  6. Delete opens Deactivate Supplier. Confirming Deactivate clears that supplier's product defaults and purchasing links so low-stock reorder drafts stop using it.
  7. Use Import CSV for bulk supplier records, following the downloadable template.

Use the Tax, Jurisdictions, and Exemptions pages

Tax combines selected-store policy with organization-wide history. Exemptions is a separate customer-certificate page:

  • Tax opens Rates & Rules for store-tax readers, or Org Jurisdictions for account-only readers. Historical Rates is a separate read-only tab; it is not the selected store's current checkout policy.
  • Jurisdictions summarizes scopes, active and retired rates, active exemptions, rate ranges, and updates on the currently loaded rate and exemption pages.
  • Exemptions manages customer exemption certificates.

Review historical rates and jurisdiction coverage

  1. Go to Tax > Historical Rates. Use Previous and Next to browse beyond the first 200 records.
  2. Select a historical rate to review its code, name, jurisdiction, scope, percentage, effective-from date, active or retired status, rate ID, and created and updated dates.
  3. Go to Organization > Jurisdictions to compare scopes, active and retired rates, exemption coverage, and the lowest and highest historical rates for each jurisdiction.
  4. Jurisdiction summaries describe the loaded pages, not organization-wide totals. Use the independent rate and exemption page controls to inspect the remaining records.

Do not treat a historical account rate as the selected store's current checkout rule. Use Store Tax Policy for current store behavior.

Add or update an exemption

Viewing requires the route access shown above. Creating, editing, or deleting an exemption requires tax.configuration.write.

  1. Go to Organization > Exemptions.
  2. Select New Exemption.
  3. Choose the Customer and exact Reason code: RESALE, GOV, NONPROFIT, EXPORT, or OTHER.
  4. Enter Jurisdiction as a US state/territory code or name, or City, ST (for example, FL or Miami, FL). Other free-form scopes are rejected. Add optional Certificate #, Effective From, optional Expires On, and optional Notes.
  5. Set Active, then select Save Exemption.
  6. Use Edit to update an existing certificate. Clearing Active retains the record with Retired status; Delete removes it immediately without a confirmation dialog.

Verify the certificate, jurisdiction, and dates before saving. An exemption record does not change a store's base category tax policy.

Manage Store Tax Policy

Reading policy and running the preview require store.tax.read. Users with store.tax.write can manage the selected store's category rules and percentage-based store-wide rules, activate or roll back category policy, and retry snapshot refreshes.

  1. Select the store in the sidebar and go to Organization > Store Tax Policy.
  2. Review Category tax rules, their readiness mode, and Store-wide tax rules. Rules show their active status and effective interval in the store's timezone.
  3. Add or edit a rule's jurisdiction and percentage. Category rules also require a category. Set the start and optional end with the date/time controls; start is inclusive and end is exclusive. A new time in a repeated daylight-saving hour uses its earlier occurrence; an unchanged schedule retains its exact stored occurrence.
  4. Clear Active to deactivate a rule while retaining it, or use Delete to remove it. Other provider rate/basis shapes remain inspectable but cannot be edited with the percentage-rule form.
  5. If checkout still uses product tax rates, resolve the listed readiness issues and select Activate category policy before expecting category and store-wide rules to take effect.
  6. If the checkout snapshot is pending, wait for any rule update to finish, then select Retry snapshot refresh. A saved provider rule is not proof that the local checkout snapshot has refreshed.
  7. Under Preview the currently effective policy, enter each line's description, category, unit price, and quantity. Optionally enter a customer ID to include applicable active exemption certificates, then select Run same-engine preview.

Compare the preview's line taxes, jurisdiction/rate attribution, and exemption reasons with the expected policy. The preview is informational; payment uses the server-owned checkout ticket. Products marked always tax exempt override category rules.

If the page says Store tax policy unavailable, Peak Support must finish the selected store's Gateway tax connection. Do not work around a missing connection or policy by altering historical account rates.

Review the Audit Log

  1. Go to Organization > Audit Log.
  2. Review the summary for outstanding and overdue invoices, payments recorded this month, low stock, open purchase orders, and draft invoices.
  3. Filter events by All events, Accounts, Inventory, Tax, Platform, or Last 7 days.
  4. Select an event to inspect its action and time, actor, area, resource, outcome, and recorded payload.
  5. Use Previous and Next to move through results in groups of 50.

The outcome badge treats ok and success as successful, pending as pending, and denied, error, or failed as unsuccessful; any other recorded outcome uses the neutral style. The on-page search and Export CSV controls are marked Coming soon; use the available filters and pagination today.

Configure the Loyalty Program

The Loyalty Program page is organization-scoped and requires org.loyalty.write.

  1. Go to Organization > Loyalty Program.
  2. Select New Program.
  3. Enter the customer-facing Program Name, Points per Dollar, Minimum Transaction ($), Points Needed for $1 Reward, and Minimum Points to Redeem.
  4. Select Create, then select Manage on the program.
  5. Under Tiers, use Add Tier or Edit to set Name, Min Points, and Multiplier.
  6. Under Rewards, use Add Reward or Edit to set Name, Points Cost, and Description.
  7. The program, tier, and reward tables also provide Delete. These controls act immediately without a confirmation dialog, so use them only when the record should be removed.

Creating a loyalty program does not enable POS loyalty prompts, contact capture, or customer-display points summaries. Settings > Settings currently exposes timezone, operating hours, and the tip prompt—not these loyalty behaviors. Contact Peak Support to change support-owned loyalty checkout behavior.

Read Loyalty Analytics

Go to Organization > Loyalty Analytics to review:

  • Total Enrollments and Enrollment Trends
  • Points Redeemed and Point Redemptions by reward
  • Customer Segments
  • Top Customers, including points, visits, and spend

If the banner says Loyalty is not enabled, the zero or empty metrics describe an inactive program, not a live program with no activity. Set up Loyalty Program and Open Loyalty Program appear only with org.loyalty.write. Top-customer names link to customer loyalty details only with org.loyalty.read; fallback Open Customers links appear only with store.customers.read.