Public and private statuses: what customers see vs what your team tracks

“What failed the quality check?” The customer has just opened an order update and is calling about a sofa that is progressing normally. Quality Check was a routine staff step. Without an explanation, it sounded like a problem.

Private statuses describe the work your team is doing. Public customer groups explain the stage the customer has reached. OrderPilot lets staff keep detailed statuses while customers see the group's name and text. A useful public stage tells the customer what has happened, what comes next, and whether anything is needed from them.

General information, not legal advice.

Give each audience the detail it needs

Purchasing needs to distinguish a PO sent from an acknowledgment checked. Receiving needs to distinguish accepted pieces from outstanding pieces. Your customer needs to know whether the sofa is progressing as expected and whether the delivery plan has changed.

Those needs belong on the same order, but they do not require the same wording. “QC hold” can be meaningful shorthand to the person managing a vendor conversation. It leaves a customer guessing about a problem they have not been told exists.

The status-map guide explains how the process connects. This part is about translation: preserving the truth while making the customer-facing description useful. Plain language should reduce interpretation, not erase information the customer needs.

Put several staff steps under a customer group

OrderPilot starts with seven customer groups. The following mapping is an example to adapt, not a claim that every store begins with these exact assignments. Out for delivery is a store-added example.

Pending Review, Changes Requested, and Rejected usually belong to the internal review process. Before showing any of them publicly, ask whether the customer can understand the actual action needed. A staff approval is different from a request for the customer to choose a finish.

The names of built-in system statuses stay fixed, while custom statuses, non-system defaults, and customer groups can be renamed. Customer-facing group wording is where your store can explain a stage in its own voice.

Write group text that answers the next question

Begin with the fact the customer can rely on, then state the next event or action. Avoid a time estimate unless it fits the particular program or order. “Most pieces spend six to ten weeks here” becomes another promise when the chosen fabric takes longer.

Use these sample rewrites as wording patterns. Replace the timing and arrangements with the actual information for the order.

The specific noun does useful work. Chairs tells the customer which goods have arrived. Our store distinguishes warehouse arrival from home delivery. A staff member may understand “shipped” instantly; the customer should not need to solve the destination.

Keep internal abbreviations out of public wording. PO, ack, QC, and hold save space on an office note but create work in a customer email. The sofa already has an assembly specification. Its progress message should not need a glossary.

Keep private review private, and customer decisions explicit

Pending Review can remain internal while a manager checks the store's decision. If the customer needs to supply a measurement or choose a different fabric, send a message naming that action. “Changes Requested” alone does not say who should do anything.

A customer's requested change also deserves an answer in the conversation. Staff review it before changing the order. The public stage can remain appropriate while the message explains the specific request and its effect. Avoid changing a whole group description to answer one customer's question.

That approach also answers the delayed-order wording question. For a single delay, send an order-specific email explaining the facts while preserving a truthful broader stage. If delays are a recurring, meaningful stage in your process, create a visible Delayed group or status arrangement with its own wording. The delay-message guide covers the message itself.

Make delays and partial arrivals visible when they affect the promise

A hidden staff status should never hide a changed customer commitment. If the delivery window moves or only part of an order can be supplied, explain which pieces are affected and what happens next.

For covered New York sales, GBL §396-u addresses delivery estimates, delay notice, and customer options, with an exclusion for substantially custom-made or custom-finished furniture. New Jersey's N.J.A.C. 13:45A-5.1 requires written notice before a promised date cannot be met, offering cancellation with a full refund or a specified later delivery.

Those rules are more specific than changing a portal label. Check with your attorney when setting your notice procedure; the delivery-date laws guide discusses jurisdiction and scope. OrderPilot keeps the communication and order record available for the team.

Show the same order clearly in OrderPilot

On Professional, manage the workflow grouping in Settings › Quotes & orders › Statuses. Staff see statuses under customer-group headers; the group editor supplies the public name and explanatory text. Customer portal access is on Growth and Professional. A hidden status keeps the last stage the customer saw, or In progress if there is no earlier customer-visible stage. Staff still see their detailed status on the order. Read that public result during testing so a hidden administrative step does not leave a misleading old stage on display. Customer group names appear in status emails as well as the portal. Status notification settings and the connection's email choice control whether a move sends a message. An internal move can remain quiet while a meaningful customer milestone sends its update. Use email for tailored explanations. Where enabled on the supported plan, status SMS uses fixed wording. The order-update templates show how to write the fuller email around the customer's actual situation.

Read the result as someone waiting for furniture

Open a sample customer's order at each stage and use this short review:

1. Can the customer identify which piece the update describes?
2. Does the stage say what actually happened?
3. Is the destination or next arrangement clear?
4. Does the message say whether the customer needs to act?
5. Would a delay or partial arrival still be explained plainly?

Keep payment and fulfillment facts distinct from the customer wording; the Shopify status comparison explains why. Finish by testing the whole status map with the public message beside the staff step.

Sources

1. General Business Law §396-u: merchandise delivery — New York State Senate; statute revision September 22, 2014.
2. N.J.A.C. 13:45A-5.1: delivery practices — New Jersey Administrative Code, reproduced by Cornell Legal Information Institute; amendment effective January 17, 2012.