One way of working across every showroom
Standardize the sale, the handoffs, and the meaning of a status while preserving the details that genuinely belong to each location.
The OrderPilot team·
At the downtown showroom, the associate asks for a 50% deposit and sends a quote with the old address. At the suburban showroom, the request is 30%, an easy 10% discount is part of the conversation, and the warranty card has been photocopied until the small print resembles upholstery texture. These figures describe an illustrative store, but the operational problem is familiar: the company has several doors and several versions of the sale.
Agree which decisions belong to the company and which genuinely belong to a location. Then apply the shared rules, document the exceptions, and test a customer’s journey between showrooms. OrderPilot keeps locations, brands, access, and the order workflow connected inside the Shopify store.
Standardize the decision before standardizing the screen
A common screen does not guarantee a common process. Staff can use the same quote form while applying different discount habits, release rules, and definitions of “ready.” Start with those decisions rather than with the appearance of the paperwork.
Ask each location to walk through an ordinary special order. What must be settled before the quote is sent? Who approves a price exception? What evidence allows purchasing to proceed? Who tells the customer about a delay?
Compare the answers without treating every difference as a failure. One showroom may have developed a useful practice another should adopt. Another difference may exist only because a manager made an exception that gradually became the local rule.
Write the agreed process in plain language. “Ready for delivery means the goods have arrived, passed the store’s check, and have a clear payment position” is more useful to training than an unexplained status label.
Separate shared rules from local details
The following matrix is a suggested operating model. It helps managers decide where consistency is necessary and where a local difference serves a real purpose.
| Area | Shared company or brand decision | Detail that can stay local |
|---|---|---|
| Quote | Required specification and terms | Location address and contact |
| Deposit | Policy by product or commercial arrangement | Person handling the request |
| Discounts | Authority and reason expectations | Manager covering the decision |
| Purchasing | Release requirements and destination definitions | Actual receiving warehouse or store |
| Receiving | Accepted, rejected, and outstanding quantity practice | Staff and appointment arrangements |
| Customer updates | Meaning of stages and communication standard | Accurate location details |
| Access | Responsibilities attached to each role | Locations assigned to the person |
| Branding | The identity and terms of each brand | Approved local logo and receipt details |
A local exception should explain why it exists, who approved it, and when it should be reviewed. Avoid exceptions whose only explanation is “that is how this location has always done it.”
The goal is a process a colleague can recognize when covering another store. The colleague may need a different phone number or warehouse address. They should not need to relearn what a signed order means.
Give every brand a dependable quote
A quote should identify the exact piece, its configuration, price, charges, and terms. Those expectations should hold at every showroom carrying the brand. A customer who visits another location should recognize the same commercial agreement.
Use a common approach to describing fabric, finish, dimensions, and delivery. Decide which details belong in the configured line, which belong in an order field, and which require a customer message. Keep the specification explicit enough for purchasing to continue without calling the original associate.
OrderPilot carries configured pieces and standard Shopify products on the same record. The agreed choices continue into the vendor purchasing workflow. That makes a common quoting practice useful beyond the PDF itself.
Do not replace a settled quote simply because the customer visits another location. Open the existing record through the permitted access, review its history, and agree who will handle the next action. Keeping the record intact also helps prevent competing versions of the promise.
Use one discount policy across the business
Discount authority should describe who can approve a concession and how the reason is recorded. The same customer request should not become a different policy simply because it arrives through another showroom door.
The discount authority matrix provides a way to define the approval handoff. Put the company’s commercial thresholds in that policy, and use OrderPilot permissions to control who can override prices and give discounts.
Make coverage part of the arrangement. If a manager is away, the associate should know who can decide and what to tell the customer while waiting. An approval process that works only when the owner is standing at the desk will invite workarounds.
Keep automatic system behavior distinct from the written policy. Permission to change a price is an access decision. A store’s detailed discount bands may still require manager judgment and a recorded review.
Choose deposits by the sale, not by the showroom habit
A deposit policy should reflect the product commitment, customer arrangement, and payment route. Different terms can be justified, but the justification should travel with the sale rather than depend on which location happens to write it.
For the example stores, management might decide that the same made-to-order category uses the same agreed payment schedule. A stocked floor piece collected immediately can follow a different arrangement because the transaction is different.
OrderPilot supports signature and deposit requirements by product or category. Native minimum-deposit requirements need Shopify Plus; on any Shopify plan, enabled deposit orders provide a separate Admin payment-link route before placement. Decide how the store’s release procedure handles its actual route before promising a standard deposit experience. Train associates to explain the amount due now, the remaining balance, and the next event. The customer should hear the same meaning at both locations even when a different authorized colleague creates the payment request.
Make manager review a shared handoff
Review should have a common purpose. Decide which orders need it, what the reviewer examines, and what happens when changes are requested. A review queue is useful when the people on either side understand the handoff.
OrderPilot’s review workflow lets the authorized reviewer approve, reject, or request changes where the feature is enabled. Use that workflow for the store’s agreed review process, and give managers consistent expectations about the evidence they need.
A reviewer should see the specification, terms, customer acceptance, and payment position appropriate to the sale. Avoid making one location’s manager reconstruct information that another location habitually keeps in private email.
Track repeated reasons for returning work. If several showrooms omit the same finish detail, the answer may be better template setup or training, not a more forceful reminder at the next meeting.
Keep brand identity and location identity accurate
A brand answers whose customer experience the document represents. A location answers which showroom or business details belong on it. Group the store’s locations under the appropriate brands rather than using a single copied document for every situation. OrderPilot supports brand kits and brand-specific documents and email designs. Location details supply the appropriate address, contact information, and other approved business information. The locations and brands guide explains how those records work together.
Merchants can maintain the brand section, location and bank details, terms, salesperson display, and reference information; advanced PDF fonts, colors, columns, and layout controls require staff-enabled access. Keep the document review focused on the customer’s actual agreement and the details the team maintains. If two locations carry different brands, use the supported brand grouping and review the output for each. Shared operational rules can remain consistent while the customer sees the correct brand’s paperwork. The multi-brand document guide covers that distinction in detail.
Give local receipt details a named owner
A local phone number, address, or receipt term is a small field with a long reach. Give someone responsibility for maintaining it when the store moves, changes contact arrangements, or updates the terms customers receive.
OrderPilot location settings support the location’s logo, receipt terms, and terms QR. Review the printed result as well as the settings screen. A field can be correct while the printed presentation still needs attention. Use the location settings guide when reviewing those details. Keep the short receipt wording consistent with the full terms it points to.
Choose a shared numbering approach that makes records easy to identify. The number or reference should help staff find the same sale across conversations and documents, rather than encourage a separate local numbering habit outside the system.
Make statuses mean the same thing everywhere
A status should tell the next person what has happened and what still needs work. If one location uses “ready” for a vendor’s shipping estimate and another uses it for goods physically checked in the warehouse, the shared label hides a serious difference.
Use OrderPilot’s status map to organize the common process. Define the connections between steps and the conditions that permit them. Distinguish automatic events from staff actions, and test the intended transition on a representative order before publishing the workflow.
Built-in statuses keep their names; merchants can name their custom statuses and customer-facing groups. The customer should receive a clear public stage while staff keep the operational detail needed to complete the work.
The status-map guide follows that design. Use customer-facing wording that makes sense without an explanation from the original salesperson. Then configure the stage updates to match real progress.
Standardize purchasing destinations and receiving evidence
Purchasing needs a consistent answer to where goods should go. Distinguish store delivery, warehouse receipt, and dropship arrangements. A destination name that means different things to different locations is an invitation to send the right sofa to the wrong place.
OrderPilot creates vendor POs from sold configured lines and supports the appropriate delivery destination. Review the actual address and instructions rather than relying on a familiar warehouse nickname.
Receiving should record what arrived, what was accepted or rejected, and what remains outstanding. Partial shipments need the same treatment across the stores so an order is not marked complete merely because a carton arrived.
Keep the vendor conversation with the PO where reply capture is configured. The colleague receiving goods should be able to understand a substitution, backorder, or damage discussion without finding the person who originally emailed the vendor.
Let associates sell another location’s stock deliberately
An associate can use OrderPilot’s POS stock and source choices to work with local stock, another location’s stock, or Order New. That helps the store offer a piece across showrooms without pretending every sale is a new vendor order.
The stock choice does not replace the physical handoff. Identify which unit is being sold, its condition, where it is now, and how it will reach the customer. A floor model may need inspection and an explicit condition agreement.
Agree which location communicates with the customer and which team releases the piece. Keep the delivery or pickup arrangement accurate on the order. If a transfer or collection must be coordinated, assign it rather than assuming the source store will infer the plan.
Use the guide to selling another showroom’s floor model to make that coordination concrete. The customer should not have to call both stores to find out who is bringing the chair.
Give floating staff the reach their work requires
Roles should mean the same thing across locations, while each person receives the location assignments needed for their actual work. A colleague covering several showrooms may need broader reach than an associate who works at one.
OrderPilot separates viewing from changing records and supports reach based on assignment, the person’s locations, or wider store access. Use the narrowest practical scope that allows the agreed service. A customer visiting a second location should be able to receive help without automatically changing sales credit. Reassignment, responsibility for follow-up, and commission attribution are separate decisions.
The roles and permissions pillar covers the matrix. Test the role of a floating associate as carefully as a permanent employee’s role; temporary coverage is where unclear assumptions tend to become visible.
Compare results using the same definitions
Start store comparisons with consistent definitions of the period, sales event, and amount. Placed order value, delivered merchandise, and cash received answer different questions. A location with long project lead times can look very different depending on the measure selected.
OrderPilot tracks quote and order values over time, and Sales performance reports quotes, orders, revenue, average order, and salesperson results with CSV export. Use the report to review the available measures, then reconcile any location comparison to records carrying the location information you need. Do not treat a salesperson comparison as a location dashboard when people work across showrooms. Decide how the business attributes cross-location sales, and apply that rule consistently in the analysis.
Review margin and workload alongside volume. A trade-heavy showroom may produce large projects with substantial design and coordination work. A smaller ticket does not automatically mean weaker selling, and a large ticket does not tell you how much service remains.
Use the numbers to ask better questions: Are quotes being completed? Are customers waiting for approvals? Are purchasing gaps concentrated in one handoff? The next action should follow the evidence, not the ranking alone.
Follow a customer between two showrooms
Return to the example company. A customer begins a sectional quote downtown, then visits the suburban showroom to see the chosen fabric beside a different leg finish.
The covering associate opens the existing quote with the appropriate permission and reviews the saved configuration. The customer’s requested finish change is recorded on that sale. The associate does not start a second quote merely because the first was created elsewhere.
A manager handles any price exception under the shared authority policy. If the customer-facing agreement changes after signing, the team obtains the required new signature. The payment reviewer reconciles what has already been received before sending another request.
Purchasing uses the agreed configuration and the selected destination. Customer-facing updates follow the same stage definitions. The two locations can divide the work while preserving one understandable account of the sale.
The example succeeds because the responsibilities are clear. A shared system helps people carry them out; it does not choose the commercial policy on their behalf.
Use a practical month to establish the common process
The following 30-day schedule is an example implementation plan, not a promise about setup time. Adjust it to the number of locations, the current records, and the team’s availability.
| Example period | Work | Evidence that it is ready to move on |
|---|---|---|
| Days 1–7 | Compare current quoting, payment, discount, and handoff practices | Written decisions on shared rules and justified exceptions |
| Days 8–14 | Review brands, location details, requirements, roles, and documents | Sample records and documents checked for each location |
| Days 15–21 | Test ordinary, changed, and cross-showroom sales | Staff can complete the scenarios and explain approval handoffs |
| Days 22–30 | Roll out, review exceptions, and correct training or setup gaps | Named owners for unresolved work and an agreed review rhythm |
Choose one representative order for each meaningful path: a new special order, a stocked piece from another store, a partial receipt, and a customer change. These examples expose more than a tour of the settings pages.
Keep the first rollout narrow enough that managers can support it. Record questions as they occur and decide whether each requires a policy decision, a setting change, or clearer training. Avoid solving the same question separately in every showroom.
Keep the standard alive after rollout
Assign an owner for shared settings and a local owner for each location’s details. When a policy changes, explain the reason, update the shared procedure, and review a sample order through the changed path.
Use recurring exception reviews to find drift early. Look for repeated manual workarounds, documents corrected outside the record, and approval habits that differ by location. Ask staff why the workaround exists before removing it.
Preserve local knowledge that improves the common process. The best receiving practice may come from the smallest showroom, and the clearest customer explanation may come from a weekend associate.
Finish with the locations and brands setup, then test what the customer actually receives. Every showroom can have its own character while the company keeps a dependable way of working.
Every showroom can have its own character while the company keeps one dependable way of working.