Skip to content
Log in

Save a POS cart as an unpaid order

On this page

Your POS staff can Save & exit a register sale, and keep it on the store as an unpaid order. This is helpful for pay-later orders, or where a customer makes a deposit and pays the balance later.

This feature is off by default, because enabling it impacts your whole order pipeline. We recommend reading the section about POS orders that have been saved below before you turn it on.

Before you start

  • You need edit access to the Store record and its Store Variables related list.
  • Choose a low activity time as POS reads store variables during the required sync. See manage POS data sync.
  • Review the section about POS orders that have been saved below, to check if this feature suits your needs.

Turn on save and exit

  1. Open the Store record and go to the Store Variables related list.
  2. Click New.
  3. Enter a Name that makes sense to your organization, such as POS save unpaid orders.
  4. Enter pos.checkout.save_incomplete_order in Key. Keys are case sensitive.
  5. Enter true in Value. Any other value leaves the feature off.
  6. Save the record.
  7. Sync the register, or wait for the next store sync.

At the register, checkout on a cart with items now offers Save & exit alongside Back.

What an operator sees

  1. With items in the cart, the operator selects Pay to start checkout.
  2. Then they select the Save & exit option.

The cart becomes an order with a status of Incomplete, carrying any payments already taken, the register clears to a fresh cart, and the operator lands on the order’s summary screen.

The order is then added to the Orders list, ready to be found and paid later. See look up a customer’s order history.

Once a partial payment has been taken on a plain cart, the Back function is no longer offered, because leaving would abandon a sale that has money against it. Save & exit gives the operator a way out that keeps both the order and the payment.

Which carts are excluded

Save & exit is withheld rather than shown as unavailable, so an operator sees it only where it works.

Cart Why it is not offered
A cart with nothing in it There is no sale to save
A cart that owes the customer money, such as a refund or an exchange still owing a payout The same carts where pay by link is unavailable
A checkout reached from an existing order, such as taking a payment on an order or paying for a fulfillment The order already exists, so Back is the exit
A cart already linked to an open order Open orders have their own exit, Submit & exit
Offline, a cart holding a rental, or one whose most recent payment is a voucher or account credit These cannot be saved unconfirmed, so the conversion waits for a connection

Offline, every other cart can still be saved, and the order is sent when the connection returns. See take payments while the POS is offline.

About POS orders that have been saved

Saved orders are real orders, not drafts. Everything that normally happens when an order is created happens now (regardless of payment):

  • Items routed to a fulfillment station produce their station tickets, so a kitchen or packing bench starts work.
  • Tax documents are committed, which for an external tax provider means a filing against a sale that has not been paid for.
  • Promotion usage is counted against any promotion on the cart, which counts toward a promotion’s usage limits.

The feature suits a trade desk raising an order to be paid on account, and it suits taking a deposit, but on a busy hospitality counter an abandoned cart saved by habit sends food to the kitchen.

:::warning An unpaid saved order is indistinguishable to the rest of the platform from an order that is about to be paid. If your store files tax with an external provider, or runs promotions with usage limits, confirm with whoever owns those before turning this on. :::

Save and exit, park, and open orders

There are three different ways to put a sale down.

  Where the sale is held Reaches a station Can another register take it?
Park cart On the store, as a cart, not an order No Yes, any register in the same store, by resuming it
Save & exit On the store, as an unpaid order Yes, on saving Yes, by finding the order
An open order On the store, as an order added to over time Yes, on each submit Yes, by resuming it

Park is the one to reach for when nothing should be committed. See park an order.

Example

A trade counter wants staff to raise an order a builder will settle on account at the end of the week.

Name Key Value
POS save unpaid orders pos.checkout.save_incomplete_order true

Once the store has synced, add an item at the register, select Pay, then Save & exit. The order summary opens with a status of Incomplete, and the order appears in the Orders list with no payment against it.

Was this article helpful?

Was this article helpful?