Quotes, invoices and POs: giving each reader the details they need

The vendor needs the fabric code and delivery destination. The customer needs the furniture they chose and the amount they're being asked to pay. Your bookkeeper needs the invoice as it stood when a payment was recorded. One order has several readers.

OrderPilot builds different documents from that shared record. The job is to maintain the information each reader needs and send the right document at the right moment. A customer quote, a vendor PO, and a technician's job sheet should agree about the furniture while serving different purposes.

Give the customer the agreed furniture and the next action

A quote or sales order should let the customer recognize the piece without decoding the store's internal shorthand. Include the model, selected options, quantities, and useful product or swatch images.

The customer also needs the commercial arrangement: named charges, discounts, relevant terms, payment information, and how the furniture will reach them. A pay button is useful when payment is available on the order and the customer understands what the request covers.

Expected timing deserves plain wording. Option lead time doesn't automatically print on the quote PDF, so communicate the agreed estimate explicitly and review any note intended to appear on the document. Keep a production estimate distinct from a booked delivery appointment.

Customer documents don't include OrderPilot's internal cost view. The same cost information is kept out of customer emails and the portal. That allows staff to review margin internally while the customer sees the selling price and the agreement.

For the wider look across these touchpoints, use the shared branding guide. Recognition should help the customer find the information, not compete with it.

Choose which salesperson appears on the paperwork

The salesperson display can use the primary salesperson, all credited salespeople, or none. Choose the setting that gives customers a useful contact without confusing responsibility.

A sale worked by several associates may benefit from naming the team. Another store may prefer the location's shared contact details and no salesperson on the document. The right choice depends on how your team actually handles follow-up.

Keep document display separate from internal attribution. Hiding a name from customer paperwork doesn't mean the store should stop tracking who worked on the sale. Review the selected output after changing the display setting.

This is particularly useful for long projects. The person covering the customer's question can use the shared order record even when the original associate is away, and the customer still has a clear way to reach the store.

Give the vendor a buildable specification

A vendor PO should state what to supply, how much to supply, and where it should go. For configured furniture, the exact option rows matter as much as the product title.

OrderPilot carries the configured specification into the PO. The vendor's SKU can be included where that vendor wants it, controlled through the vendor's SKU-on-PO setting. This avoids forcing a code onto paperwork for a maker that works from a different identification system. Review the requested delivery date and vendor contact information alongside the lines. A requested date tells the vendor what the store needs; it isn't proof the vendor accepted that date. Keep the confirmation with the PO conversation. The PO carries its document date and salesperson information. Staff can add a customer or project reference in Vendor notes when the vendor needs it. Per-line customer order numbers and the Side Label field don't print on the PO PDF, so put necessary references in the vendor-visible notes and inspect the generated file.

The furniture PO checklist covers the specification and destination in more depth.

Show the destination the vendor actually needs

A PO can be directed to the store, a warehouse, or the customer through the appropriate delivery arrangement. Direct shipment to the customer is therefore possible, but it needs an intentional destination review.

For store delivery, the vendor needs the receiving location and practical instructions for that delivery. For dropship, the customer's delivery details become necessary to complete the job. The rule is to share what the chosen route needs, rather than assuming every vendor always needs every customer detail.

Review mixed customer orders carefully. A PO that gathers several sold lines doesn't necessarily have one customer destination. Keep the ship-to choice and the source orders clear before sending.

If the delivery address changes after the PO has gone out, treat that as a vendor communication task. An edited customer record alone doesn't establish that the maker or carrier has received and accepted the change.

Let the invoice preserve the payment history

An invoice tells the bookkeeper what was billed and what payment position the document records. Numbering helps identify it, while frozen versions preserve the history when the order later changes.

Before payment, edits update the current unpaid invoice. The first payment freezes a paid or partially paid copy. That older copy remains part of the record rather than being silently rewritten to match every later order edit. Suppose a sample order is $4,000 before tax, and the customer pays $2,000. The frozen invoice records that stage. Later, an agreed $300 service is added. The current order can show $4,300 and a $2,300 balance, while the earlier invoice still reflects the original $4,000 arrangement and its payment.

That older total isn't automatically an error. It is evidence of what the document said at that point. Use the current record for the current balance and the earlier version to explain the history. Don't replace the earlier copy merely to make every document display the same number.

Location-specific wire instructions and payment details should also be maintained at their source. The invoice should direct a customer to the correct payment arrangement for the selling location.

Give a technician enough detail to complete the visit

A technician's job sheet should explain the visit, the affected furniture, and the work to perform. OrderPilot's optional warranty module provides printable job sheets connected to the service work.

The sheet can carry visit details, parts, photos, and the amount the technician is permitted to collect. That last point needs careful reading: a repair visit's authorized collection is not an invitation to collect whatever the original order still shows as outstanding. Include photos that help the technician find the problem and identify the correct part. A close view of a damaged hinge can be more useful than a beautiful full-room photograph in which the cabinet is an enthusiastic supporting actor.

Use the technician job-sheet guide for the complete handoff. The order supplies context, while the job sheet makes the day's task clear.

Keep product terms attached to the right agreement

Product and category terms explain conditions that don't belong on every sale. A special-order upholstery condition can follow the relevant product, while a location supplies the store's general terms.

Review an order containing different kinds of furniture. Final-sale wording for a floor sample shouldn't leave the customer wondering whether every other piece carries the same condition. Read the assembled terms as a customer would, with the relevant line in mind.

The signed record freezes the agreement. If a customer-visible change requires a revised signature, the new document should make that change clear while the earlier evidence remains available.

Validity is another field worth reading rather than assuming. The default quote validity counts from creation, and resending doesn't restart it. The quote-validity guide explains how to handle an older quote returning to the desk.

Review the output from each reader's chair

Maintain the source data, then inspect the document that will actually leave the store. Merchant controls cover brand and location details, terms, salesperson display, and references; advanced fonts, columns, headers, and appendix design are switched on per store by the OrderPilot team.

Use this reader checklist before sending or printing:

The checklist is a review standard, not a promise that every field can be rearranged in a self-serve designer. Its purpose is to make the existing outputs useful to their readers.

Before the next order leaves the desk, open the customer PDF and vendor PO side by side. They should describe the same furniture and make different jobs easy. Continue with which document goes when to place each one in the sale.