Furniture Store POS: Deposits, Special Orders and Balance Due

A furniture store POS has to take a deposit today, hold a special order for weeks, and collect the balance when the piece is ready or delivered, without losing track of what the customer owes or what you owe the vendor. If it can only ring a sale and take full payment, you will run the real business in a notebook.

This guide covers the parts of furniture retail that general POS systems handle badly: deposits and balance-due orders, special orders, and returns on large-ticket items. It also explains what Retailer OS does for each. For a broader buying view, see our guide to the best furniture store POS.

How should a furniture store take a deposit?

A deposit is a partial payment taken now against a sale that completes later, and until the goods are delivered it is money you owe the customer, not revenue. That one sentence changes how you should record it.

Most furniture is sold in three payment moments: a deposit when the customer commits, sometimes a second payment when the piece arrives at your warehouse, and the balance at pickup or delivery. Your POS should link all three to one order, so staff can open it and see the total, what is paid and what is due.

Set deposit rules in writing before you need them:

• Standard stock items: a smaller deposit, such as 20 to 30 percent, or full payment.
• Special orders and custom pieces: 50 percent or more, and non-refundable once the vendor has the order.
• Large-ticket sets, such as a full living room: stage the deposit by item.
• The date by which the balance must be paid, and what happens if it is not.

Do the math on the deposit before you quote it. A sofa sells for $2,400 and costs you $1,200 from the vendor. A 50 percent deposit of $1,200 covers your cost. If the customer cancels after you have ordered, you are not out of pocket, even if you can only resell the piece at a discount. A 20 percent deposit of $480 leaves you $720 short on a custom piece you cannot resell.

How do special orders work in a POS?

A special order is a sale of something you do not have on the floor: a different fabric, a custom size, or a piece the vendor builds after you order. It is a sale, a purchase and a delivery promise tied together, and each of the three has to be tracked.

The flow looks like this:

• Create the order with the exact item, fabric, finish, size and price the customer approved.
• Take the deposit and attach it to the order.
• Place a purchase order with the vendor, and note the quoted lead time.
• Receive the piece against the purchase order when it arrives, and check it for damage before the customer sees it.
• Contact the customer, take the balance and arrange pickup or delivery.

The failure points are predictable. A special order is placed with the vendor but never linked to a customer, so a sofa arrives and nobody knows whose it is. A deposit is taken but the order is lost between the sales floor and purchasing. The customer is never called because the receiving staff did not know a customer was waiting. Whatever system you use, make sure the customer, the deposit and the purchase order are tied to each other.

A worked example

A customer orders a $3,200 sectional in a fabric you do not stock. Your cost is $1,700 and the vendor quotes eight weeks. You take a $1,700 deposit, which is 53 percent of the price and covers your cost. You place the purchase order the same day and write the customer’s name on it. In week eight the sectional is received, and you check it for damage and call the customer. They pay the $1,500 balance, plus a delivery fee, and you book the truck.

Nothing in that chain is hard. The risk is in the gaps between the steps: a deposit that is not tied to a purchase order, a received piece nobody connects to a customer, a balance that is forgotten once the piece is in the warehouse. A good weekly habit is to review every open special order, sort by age, and call anyone whose order is more than a week past its promised date. It costs an hour and saves a refund.

What about delivery scheduling?

Delivery is where many furniture stores spend the most time on the phone. A system that tracks the order status well makes the calls shorter, but delivery itself is often a separate job with a truck, a crew and time windows.

Treat delivery as its own question when you evaluate software. Ask whether the POS can show the orders that are paid in full and ready, whether it can record a delivery fee as its own line on the sale, and whether it records the promised date. Do not assume it schedules routes or crews. If it does not, a shared calendar and a printed daily list still work, as long as the order record is the source of the list.

How should you handle returns on large-ticket items?

Returns on furniture are not like returns on a shirt. The item is heavy, may be damaged in transit, and may be a special order you cannot resell. Your policy matters more than your software, but your software has to carry it out.

A policy worth writing down:

• Stock items: return within a set window, in original condition, with a restocking fee if you charge one.
• Special orders and custom pieces: final sale once ordered, apart from defects.
• Damage: photos at delivery and a note on the order, so you can claim from the vendor.
• Refund method: back to the original payment, or store credit if the customer chooses it.

Limit who can refund. A refund of $2,400 is a large amount for a cashier to approve alone. Make refunds, voids and price overrides separate permissions, so a salesperson can sell and a manager approves the rest. Ask also how the POS handles a return on an order that was paid in parts, because the refund may need to go back to more than one payment.

One more trap is the store credit refund. Furniture buyers who return a piece often want credit toward a different one. That is fine, but record it as store credit on the customer, not as a manual price cut on the next sale, so the numbers on both orders stay true and you can see how much credit is outstanding.

How should deposits and sales reach your accounting?

The right accounting treatment of deposits, and when sales tax applies to them, depends on where you operate and how your accountant sets up your books. Ask them before you go live, not at the end of the year. What you can do is make sure your POS keeps clean records: a deposit tagged as a deposit, the final payment tagged as the balance, and the sale dated by when the goods leave.

If you use QuickBooks Online, find out exactly what the sync sends. In Retailer OS, a daily sales journal per channel and received purchase orders as bills go to QuickBooks Online. Retailer OS is not your accounting system, so the books themselves stay in QuickBooks. For more on this, see our explainer on the QuickBooks Online sync for retailers.

How does Retailer OS handle a furniture store?

Retailer OS has dedicated flows for furniture retail, covering special orders and deposits, and it runs them on the same inventory and purchasing the rest of the store uses. These are the facts that matter.

• Special orders and deposits as a dedicated furniture flow, alongside normal counter checkout.
• Mixed tenders and split payments across cash, card, gift card, store credit and customer account, so a customer can pay a balance with more than one method. Returns and exchanges are part of the register.
• Purchase orders to vendors and receiving against them, with cost tracking, plus per-item, per-location stock and a movement ledger.
• Variants for fabric, finish and size, and serial-number tracking for pieces that need it.
• Customer accounts and customer profiles with purchase history, and the option to put a trade customer on credit terms.
• Roles and permissions. Refunds and returns, voids, discounts and price overrides are separate permissions, and an audit log records who changed what.
• Inter-location transfers with in-transit tracking, useful when a showroom and a warehouse hold different stock.
• Card payments on your own Stripe account, with Stripe Terminal readers at the counter. Retailer OS takes no platform fee and no cut of sales.

Be clear about what this post does not claim. Delivery routing and crew scheduling are not listed among the product features, so treat them as a question for any system, including this one. Retailer OS does schedule your staff’s shifts and keeps a time clock, which is a separate thing.

The online store, at $99.99 a month, is a separate paid add-on on the same catalog and inventory. It supports buy-online and pickup-in-store, which suits in-stock accessories and small pieces. Pricing for the core system is $99.99 a month per store plus $9.99 a month per user seat, so the smallest bill is $109.98 a month. Each showroom or warehouse is its own store. See pricing and the multi-store POS page.