Roles and permissions for a furniture store: who sees what

The associate discounts a sectional, changes its payment terms, and asks a colleague to release the order before the signature arrives. Meanwhile, someone covering the desk opens a cost report to answer a delivery question. With loose access, an ordinary Tuesday can produce decisions nobody meant to delegate.

A workable permissions plan gives each person enough access to finish the job and a clear way to get an exception approved. Write the store’s matrix first. Then use OrderPilot’s roles, record reach, and location assignments to put those decisions into practice.

Give people access for the job they actually do

A job title is a starting point, not a permissions specification. “Sales manager” might mean coaching the floor at one store and controlling pricing, customer escalations, and staffing at another. List the tasks before selecting the permissions.

For a sales associate, that usually begins with preparing an accurate quote, finding the customer’s existing work, explaining terms, and handing the sale forward. For purchasing, it begins with reviewing what was sold, placing vendor orders, and managing replies. Those jobs overlap on the order record without needing identical control over it.

Separate routine work from exceptional decisions. If an associate can prepare a quote but a manager must approve an unusual discount, the handoff needs a named approver and a usable response process. A restriction that sends everyone searching for an absent owner will quickly become pressure for broader access.

The point is predictable authority. Trust grows when staff know what they may decide, what they should escalate, and where the next person will find the explanation.

Identify the actions that can change the store’s position

Sensitive actions are not limited to the Refund button. A price change, an altered payment arrangement, or a reassigned sales credit can matter just as much to the people responsible for the sale.

Include these decisions in the matrix:

• Viewing item costs and profit information.
• Overriding prices and giving discounts.
• Setting payment terms and requesting or recording payments.
• Refunding money.
• Bypassing signature or deposit requirements.
• Approving warranty exceptions.
• Reassigning records and changing sales credit.
• Viewing commission information.
• Changing settings or another person’s access.

For each action, identify who performs it, who reviews exceptions, and what record explains the decision. Keep those responsibilities distinct even where the same person covers several jobs.

Do not treat permission as proof that an action is commercially wise. Someone authorized to refund still needs the correct order, reason, and payment history. The permission establishes authority; the workflow supplies the facts needed to exercise it.

Start with a matrix your team can discuss

The following is a suggested starting policy, not a description of OrderPilot’s default roles. Adapt it to the responsibilities in your store. “By approval” describes your operating procedure; it does not promise a separate automatic approval mechanism for every cell.

Use “usually no” to invite a concrete discussion, not to avoid making the decision. If the bookkeeper also manages customer refunds, write that responsibility into the final matrix. If receiving must correct a quantity but should not change a selling price, preserve that distinction.

Avoid one sprawling role for everyone who helps in the back office. The person checking a freight invoice and the person approving a goodwill replacement may both sit behind the same door. That does not make their authority interchangeable.

Decide who can see another person’s quotes

Viewing and changing are different decisions. A colleague covering lunch may need to read the quote, answer a fabric question, and identify the next action. That does not automatically mean the colleague should change the discount or take over the sale.

OrderPilot can scope access to assigned records, location records, or wider shop records, with seeing and changing set separately. Choose the scope that allows service continuity. Then identify which actions remain restricted inside that scope.

For weekend coverage, a useful policy might let associates see the location’s work while changing only the records assigned to them. A manager can handle reassignment when a customer needs substantial help. If your selling model depends on shared editing, choose that deliberately and pair it with clear sales-credit rules.

A Mine or All list choice is a way to navigate work. It is not a substitute for permission to access the underlying records. Train the team on both: how to find an order and what they are authorized to do after opening it.

Use locations to reflect real responsibility

Location reach should match where a person works and what they are covering. A floating associate may need several showrooms; a receiving lead may need access across locations to resolve incoming goods. Give that reach because of the work, not simply because someone has been with the business a long time.

Cross-showroom sales need an agreed handoff. The customer may begin at one location and return to another, but the store still needs a clear responsible person, accurate delivery arrangements, and agreed sales credit. Access should allow the handoff without silently redefining those things.

Review customer data with the same care. Someone who needs an address for delivery does not necessarily need broad customer exports or every account’s financial information. The separate customer-data privacy guide covers the state-law questions; the operating principle here is to provide access for a defined purpose.

Keep Shopify and OrderPilot access aligned

Shopify’s staff controls and OrderPilot’s roles govern different parts of the work. Shopify controls access to its own surfaces and actions. OrderPilot controls what the person can do within the app and its POS screens.

Shopify lists staff roles and permissions among the features of POS Pro. Review the register’s Shopify permissions alongside the OrderPilot role, especially for payments and refunds. Restricting an action in the app should not be treated as a complete review of every route available elsewhere in Shopify.

If a person cannot complete a task, examine both layers before broadening access. The missing step might be a Shopify permission, an OrderPilot action, record reach, a location assignment, or a feature the store has not enabled. Giving administrator access to investigate one blocked action is a poor long-term policy.

Test with the actual role on the surfaces that person uses. Do not assume a successful check in Shopify Admin proves the showroom iPad behaves the same way.

How to do this in OrderPilot

OrderPilot starts with Store administrator, Salesperson, and Operations roles. These are editable starting points, and you can create roles that fit the store. Settings › Staff & roles brings the Staff, Roles, Activity, and Access rules areas together. Use the role editor to translate your matrix into permissions. Review pricing and terms, payment actions, costs, reports, and exceptional approvals as separate decisions. A permission to work on an order should not become an assumed right to do everything connected to it. Set record reach for viewing and changing quotes and orders. Then decide whether the role works in Admin, POS, or both. Those choices should match the actual handoff between the desk and the floor. Assign each person the appropriate locations on the Staff tab. Managers can grant only access they hold, and the owner retains full access. That provides a clear boundary around delegated access management. For roles without cost access, supplier costs are kept out of the OrderPilot screen. POS controls that are unavailable explain why, so staff can identify the blocker rather than repeatedly trying the same action. Access changes and refused actions are logged. Review those entries to understand both inappropriate attempts and legitimate work that the role may be preventing. A refusal is evidence to examine, not automatic proof of misconduct. Start implementation with the guide to inviting staff and choosing starting roles. Keep the matrix beside you while reviewing the settings; it describes the business decision each control is meant to enforce.

Test the matrix against a realistic Saturday sale

Say an associate prepares a $6,000 sectional quote and the customer requests a $300 discount. In this illustrative policy, the associate may prepare the quote but needs the sales manager’s approval for that adjustment.

The associate records the request and the reason. The manager reviews the sale, makes the authorized change, and leaves the decision with the order. Purchasing can see the agreed configuration and release requirements without receiving permission to revise the selling price.

The customer then asks to place the order before signing. That is a separate exception. Discount authority does not imply permission to bypass a signature requirement. The person responsible for the exception reviews the actual risk and records the decision through the permitted workflow.

Finally, the bookkeeper reconciles a payment received. The ability to record that payment does not need to include redesigning the customer’s configuration or changing the salesperson’s credit. Each person completes a useful part of the sale without inheriting the whole administrator role.

Walk the team through this scenario before rollout. If the manager is unavailable, the process should say who covers approval. If no authorized person is available, staff should know what they can promise the customer while the decision waits.

Separate cost visibility from pricing authority

Cost visibility should follow responsibility for margin, buying, and accounting. It should not be granted merely to make a discount conversation easier. Associates can work from clear selling prices and escalation rules without needing the vendor invoice.

The companion post Should salespeople see furniture cost? weighs when disclosure helps and when it creates confusion. It also distinguishes item cost from the full economics of freight, service, and store overhead.

Discount authority deserves its own written policy. A salesperson who can see cost is not automatically allowed to reduce the price, and a manager who approves a concession needs a defined basis for doing so. Use the discount authority matrix to settle the commercial limits and the approval handoff.

Keep compensation decisions distinct from access

A compensation plan answers how people earn. A role answers what they may see and change. Link the two carefully: an associate may need to see earned commission without needing to edit rates, change splits, or open the store’s broader profit information.

Begin with commission structures compared when choosing among straight commission, a draw, base-plus, and salary. Then define the earning event with the guide to written, delivered, or paid sales. A payment schedule is difficult to explain when the earning event is left implicit.

The calculation base is another decision. The guide to gross, net, and margin-based commission explains how the base affects the result and how cost visibility can remain restricted. Keep the agreed formula accessible to the people paid under it.

Shared work needs documented attribution. Use the guide to splitting sales credit when an associate and an in-house designer both contribute. Permission to change the credit should belong to the person responsible for resolving the policy, not simply whoever happens to edit last.

Make customer coverage fair enough to follow

Traffic allocation affects whether staff willingly help one another. If helping a colleague feels like surrendering the next opportunity, the permissions system will inherit a people problem it cannot solve.

Review the up system and its alternatives alongside the store’s appointment and return-visit rules. Decide how walk-ins, booked clients, and absent colleagues’ customers are handled before the Saturday queue begins.

Repeat and trade accounts also need a policy. House accounts and sales credit explains how to distinguish ownership of a business relationship from credit for the current sale. Record responsibility and credit separately so the customer can receive help without reopening the compensation discussion.

Vendor incentives add another influence. Use the guide to spiffs to decide which programs staff may participate in and how managers review them. A vendor promotion should fit the store’s selling standards and recordkeeping.

Give part-timers a complete role for their work

Weekend employees need enough access to serve the customers they meet. Shorter hours do not justify a vague or incomplete role. Give them the same clear scope, escalation path, and product training as anyone doing that job.

If a family member does the books, start with bookkeeping responsibilities rather than the family relationship. They may need payment history, costs, and accounting reports. They do not automatically need to change access, approve every warranty exception, or rewrite the catalog.

For hiring, use furniture salesperson earnings to frame compensation accurately and the weekend hiring guide to make the schedule explicit. Access and training should match what you tell candidates the role involves.

Change access when the job changes

A role change changes access; it should not be treated as an instruction to erase the person’s history or rewrite who earned past sales. Review open work, assignment, locations, and sales credit deliberately when someone changes responsibilities.

The salesperson departure checklist covers live quotes, customer follow-up, and the handoff to a new responsible colleague. Preserve the commercial record while removing access the departing employee no longer needs.

Train the replacement on the actual workflow. The new-associate training plan organizes learning beyond orientation, while training long-serving staff on a new system addresses experienced colleagues changing tools. Neither group should discover the approval process through a customer-facing error.

Use the history to review decisions fairly

An activity history helps answer what changed, who made the change, and why. Start with the recorded facts when reviewing an unexpected refund, discount, or reassignment. An unusual entry may be a mistake, a legitimate exception, or something requiring investigation.

The guide to activity history and restore explains how earlier versions support review. Restoration also needs judgment: an old version may conflict with later payments, purchasing, or customer commitments, so review the consequences before applying a change.

For prevention, use internal-fraud controls for furniture stores to examine combinations of access and missing review. The goal is a process in which sensitive work can be independently checked, without turning every colleague into a suspect.

Roll out a usable policy and revisit it quarterly

Begin with the narrowest role that still lets the person complete the agreed job. Test ordinary work and an exception. Explain the restrictions in plain language, identify who can approve changes, and invite staff to report a blocker with the order and task attached.

At the quarterly review, compare the matrix with current duties, locations, and open access. Also review immediately after a departure, transfer, or change in responsibility. A scheduled review is useful; it does not replace those events.

Across locations, maintain the same meaning for a role. The guide to working consistently across showrooms covers the shared process and justified local differences. A salesperson should not gain unexpected refund authority simply by covering another store.

Finally, observe whether the process works for customers. Mystery-shopping your own showroom can reveal whether staff explain an approval wait clearly, find the right quote, and preserve the agreed details during a handoff.

Keep the finished matrix short enough to discuss at a team meeting and close enough to use at the desk. Finding the refund approver should not require a showroom treasure hunt.

Sources

1. Shopify POS pricing: staff roles and permissions — Shopify.