For retailers who run layby at the counter and want it everywhere else

Layby Integration: Taking a Counter Habit Online Without Losing Track of the Money

Layby is one of the oldest payment arrangements in Australian retail and one of the hardest to integrate well. The customer pays a deposit, you put the goods aside, they pay the balance over weeks or months, and they take the goods home only when the last payment clears. In a single shop with a layby shelf and a card file, it works. Across a website, several stores, a POS and an accounting system, every one of those steps can quietly go wrong.

The usual failures are predictable: a reserved unit that the website still thinks is available, a deposit booked as a sale in the month it was taken, a customer who started a layby in one store and cannot pay it off in another, and a layby book nobody can produce at year end. This page covers how layby actually has to work across systems, what the law expects at a general level, and when the layby feature already built into your POS is all you need.

Book a Layby Integration Call (03) 9003 0111

Layby in Numbers

3 records

Every layby lives in at once

A stock reservation, a customer liability and a written agreement, and they have to stay in step

0 third parties

Unlike buy now pay later

You hold the goods, the money and the risk the customer does not finish paying

6 to 12 weeks

A common layby term

Illustrative only, terms vary widely by retailer and category, longer around Christmas

1 report

The layby book

Outstanding balances by customer and agreement, which your accountant will ask for at year end

Four Things That Make Layby Different From Every Other Payment Type

Layby looks like a slow sale. Structurally it is a reservation, a liability and a contract, all running at once for weeks.

You carry the risk, not a provider

With buy now pay later, the customer takes the goods today and a third party pays you, less a fee, and chases the customer for the instalments. With layby there is no third party. You keep the goods until the customer has paid in full, you receive every instalment directly, and if the customer cancels you are left with goods that have been off sale for weeks and an obligation to refund what they paid, less any termination charge your agreement allows. That changes what the integration has to track.

Reserved goods are still yours but cannot be sold

A layby unit is still physically yours and still on your books as inventory, but it must not be sold to anyone else. That middle state is exactly what most ecommerce and POS stock models are worst at. If the reservation is only recorded on a paper tag in the back room, the website and the other stores will keep offering a unit that is already promised.

Money received is not yet revenue

Deposits and instalments are customer money held against a future sale. In general terms they belong in a liability account until the layby completes and the goods are handed over, at which point the sale is recognised. Booking each instalment as a sale overstates revenue, distorts margin reporting and makes a cancelled layby very messy to reverse. Your accountant should confirm the treatment, including GST timing, for your business.

It is a consumer contract with rules

Layby is specifically regulated under the Australian Consumer Law. At a general level the agreement must be in writing, the customer can cancel at any time before the goods are delivered, including after the final payment, any termination charge must be set out in the agreement and is limited to your reasonable costs, and you can only end the agreement yourself in limited circumstances, in which case no termination charge applies. The integration has to produce the paperwork and enforce the arithmetic consistently in every channel.

How Layby Has to Work Across Systems

Six mechanisms, each with a decision attached. Most of the build effort is in the edges: cancellation, cross store payment and stocktake.

Off sale everywhere

Reservation across all channels

The moment a layby is created, the specific unit leaves available to sell in every channel: the POS at every store, the website, any marketplace listing. In practice that means a reserved or committed quantity that the stock feed subtracts before publishing availability, rather than a manual adjustment someone remembers to reverse. Serialised or one off items, such as jewellery or furniture, should be reserved by serial number so the right piece is held. The reservation is released only by completion, cancellation or an authorised transfer.

Customer money held

Deposit and instalments as a liability

Each payment posts to a layby liability account, tagged with the layby reference, rather than to sales. On completion, the full sale is recognised and the liability cleared in one movement. For example, a 600 dollar bed frame with a 60 dollar deposit and nine payments of 60 dollars shows a liability that climbs to 600 dollars and then converts to a 600 dollar sale on the day of collection. Your accountant decides the exact accounts and GST timing, and the integration posts consistently to whatever they specify.

Balances that move

Schedule, reminders and missed payments

The agreed schedule is stored against the layby so the system knows what is due and when. Reminders go out a few days before each due date by SMS or email with a secure link to pay online. A missed payment triggers a polite follow up, then a second, then an internal task for a person to call. Nothing is cancelled automatically, because ending a layby for non payment is a legal decision with conditions attached, not a timer.

Cross channel payments

Pay anywhere, collect where the goods are

A layby started online can be paid in store, and a layby started in Parramatta can be paid off in Penrith. That only works if every POS and the website read the same layby record and post payments against the same reference. The goods stay reserved at the original location unless someone deliberately transfers them, and the collection point is recorded so the right store has the item ready on the last payment.

Clean reversal

Cancellation and refund

When a customer cancels, the system calculates the refund as total paid less any termination charge permitted under the agreement, releases the reservation, returns the unit to available stock in every channel and reverses the liability. Refunds should go back via the original payment method where possible, and the reason and approver should be recorded. A cancellation initiated by the retailer follows a separate, approved path, because it is allowed only in limited circumstances and no termination charge can be deducted.

Outstanding balances

Layby book and stocktake view

A live report of every open layby: customer, items, store, start date, total, paid to date, balance outstanding, next due date and days since last payment. The same data drives stocktake, because reserved units are physically present and counted as your inventory but must be identified as committed so counters do not treat them as surplus. The layby book total should agree with the liability account balance, and if it does not, something has posted incorrectly.

Layby Scenarios and How They Should Behave

Task	Traditional	Done Properly	Notes
Layby started at the counter	Paper slip, item tagged in the back room	Unit reserved in every channel instantly	This is the most important rule. If the website can still sell it, the layby is not really reserved.
Layby started online	Not offered, or a manual email exchange	Deposit taken at checkout, agreement emailed	Usually needs an app or custom checkout step, since most ecommerce platforms do not offer true layby natively.
Started in one store, paid in another	Customer sent back to the original store	Payment posted to the shared layby record	Requires a single layby ledger across stores, which some POS systems provide and some do not.
Started online, collected in store	Store has no record of the online layby	Goods reserved at the nominated store	Different from click and collect: the hold lasts weeks, and the final payment, not the order, triggers release.
Instalment comes due	Staff ring customers from a list	Reminder with a pay link sent automatically	A pay link lets the customer pay from their phone instead of coming into the store or ringing up.
Customer cancels halfway	Refund worked out on a calculator	Refund less permitted charge, stock released	The charge must be in the written agreement, applies only when the customer cancels, and cannot exceed reasonable costs. The system applies it consistently.
Final payment made	Sale rung up again at the till	Liability converts to a sale, goods released	Ringing the sale up again is a classic source of double counted revenue and wrong GST figures.
Year end and stocktake	Layby shelf counted separately, book rebuilt	Layby book and reserved stock reported	Accountants ask for the layby book. Counters need to know which units are committed.

Where Layby Integrations Go Wrong

The reservation lives only at the counter

If the POS records the layby but the stock feed to the website ignores reserved quantities, the unit stays on sale online. With high value single units this produces the worst possible customer conversation: telling a layby customer who has paid for eight weeks that their item was sold on the website. Confirm that the field your POS uses for layby commitments is actually read by the ecommerce stock sync, and test it with a real item before launch.

Instalments posted as sales

Many POS to accounting connectors push every payment as revenue because that is how ordinary sales work. For layby that front loads revenue, splits a single sale across several months, makes cancellations look like negative sales and complicates GST reporting on your business activity statement. Map layby payment types to a liability account from day one, and have your accountant confirm both the account structure and the GST attribution timing for your situation.

Treating layby law as fine print

Layby agreements are regulated under the Australian Consumer Law. Broadly, they must be in writing and given to the customer, the customer may terminate at any time before the goods are delivered, even after the final payment, any termination charge must be set out in the agreement and cannot exceed your reasonable costs, and the retailer may terminate only in limited circumstances, such as a breach by the customer, in which case it cannot charge a termination fee. This is general information, not legal advice. Read the current ACCC guidance on lay by agreements and get advice on your own terms before you automate them.

The Christmas layby season arrives untested

For many retailers layby is busiest before Christmas, as customers reserve gifts early and pay them off before the holidays. That can mean a run of new reservations in the months beforehand, final payments and collections bunched into the last weeks before Christmas, and cancellations afterwards. Test reservation sync, reminder volumes and collection workflows at peak volume before the season starts, set a clear last date for Christmas laybys, and never configure a rule that cancels overdue laybys automatically, because ending an agreement for non payment is a legal decision a person should make.

Cross store payments without a shared record

If each store keeps its own layby list, a payment taken in the wrong store lands as an unexplained credit, the original store still shows a balance and the customer is chased for money already paid. Either use a POS with a single layby ledger across locations or build one shared record that every channel reads and writes. Never reconcile it by phone call between stores.

Layby payments missing from the bank reconciliation

Instalments arrive through the same card terminals, gateways and cash drawers as ordinary sales, so they settle into the same bank deposits. If layby payments are posted to a liability account but the settlement matching only looks for sales, deposits will not reconcile. The layby payment types need to be included in the daily settlement matching, not handled as a separate side process.

How Yes AI Approaches Layby Integration

We check what your POS already does

Lightspeed and Retail Express both have native layby features, and Shopify POS can support layby through apps. Square and several others did not have a built in equivalent when this page was written. If your POS handles layby well and you only sell in store, we will say so and help you configure it rather than build anything.

Accounts and terms agreed first

The liability account, how payments and completions post, the termination charge in your written terms and how GST is handled are settled with your accountant and adviser before build. The integration then applies those decisions identically in every store and online.

Reservations and schedules run by us

Stock reservation sync, payment reminders, cross store posting and the layby book run on a managed cloud automation layer we operate, with logging of every reservation and payment and alerting if a store or channel stops syncing.

A person decides the hard cases

Overdue accounts, retailer initiated cancellations, disputed balances and stock transfers between stores go to a named owner with the history attached. Automation handles reminders and posting, and decisions with legal consequences stay with a person.

From Layby Shelf to Integrated Layby

Five steps. A retailer whose POS already supports layby can often be integrated in a few weeks. One that needs online layby built from scratch takes longer.

Map the current layby process

How laybys are created, where reservations are recorded, how payments are taken and posted, how cancellations are handled, and what the written terms say today, store by store.

Decide native, app or built

Assess the layby capability in your POS and ecommerce platform. Use the native feature where it fits, and only build the parts it genuinely cannot do, such as online layby or a shared ledger.

Agree accounts and terms

Liability account, completion posting, termination charge, refund method and GST timing confirmed with your accountant, and your layby terms reviewed against current ACCC guidance.

Build and test reservation and payments

Reservation across all channels, instalment posting, reminders, cross store payment and cancellation, tested with real items and a full cancellation and completion cycle before launch.

Run the layby book and prepare for peak

Weekly layby book review against the liability balance, overdue escalation with an owner, and capacity checks for the Christmas layby season before it starts.

FAQ

What is the difference between layby and buy now pay later?

With buy now pay later, the customer takes the goods immediately, a third party provider pays you upfront less a fee, and the provider collects the instalments and carries the risk of non payment. With layby, there is no third party: you keep the goods until the customer has paid in full, you receive the instalments directly, and you carry the risk that the customer stops paying. Layby usually costs you nothing in provider fees, but it ties up stock and creates a liability you have to manage.

What does the Australian Consumer Law say about layby?

In general terms, layby agreements must be in writing and a copy given to the customer, the customer can terminate the agreement at any time before the goods are delivered, including after the final payment, the retailer can only charge a termination fee if it is in the agreement and it must not exceed the retailer’s reasonable costs, and the retailer can only terminate in limited circumstances such as a breach of the agreement by the customer, in which case it cannot charge a termination fee. On termination, the retailer must refund everything paid, less any termination charge that is permitted. This is a general summary only. Check the current ACCC guidance on lay by agreements and get legal advice on your own terms.

Should layby deposits be recorded as sales?

Generally no. Deposits and instalments are usually held in a customer liability account until the layby is completed and the goods handed over, when the full sale is recognised. This keeps revenue in the period the sale actually happens and makes cancellations straightforward to reverse. GST attribution timing for layby can have its own considerations, so confirm the treatment for your business with your accountant before the integration is configured.

Can customers start a layby online and collect in store?

Yes, and it is one of the most common reasons retailers ask for layby integration. The deposit is taken online, the agreement is emailed, the unit is reserved at the nominated store and removed from available stock in every channel, and the customer can pay instalments online or in any store. On the final payment, the store is notified to have the goods ready. Most ecommerce platforms need an app or custom step to do this, because true layby is not usually a native checkout option.

Which POS systems support layby natively?

Lightspeed Retail and Retail Express both include layby features, and Shopify POS can support layby through apps from its app store. Square and several other POS systems do not offer a built in equivalent, so layby is either handled manually or through an external record. Native support varies in depth: some handle cross store payments and partial cancellations well, others only cover single store laybys. Check the current feature set with your vendor, because these change.

How should reserved layby stock be treated at stocktake?

Reserved layby units are still your inventory until the customer completes and collects, so they are counted and valued as stock on hand. They must also be identified as committed, so counters do not record them as surplus or adjust them away, and so the reserved quantity does not reappear as available stock afterwards. A layby book listing items by location makes the count quick to reconcile, and any reserved unit that cannot be found should be investigated immediately.

Do we need integration if our POS already has a layby feature?

Often not. If you sell only in store, and your POS layby feature reserves stock, supports payments in any of your stores and posts payments to accounting correctly, configure it well and use it. Integration earns its place when you add online layby, when your website and POS are separate systems that need to share reservations, when your accounting connector books instalments as sales, or when the Christmas layby season produces more manual reconciliation than your team can absorb.

Run Layby Everywhere You Sell, With One Set of Numbers

Book a call. We look at how your POS, website and accounting system handle layby today, tell you honestly whether the native feature is enough, and give you a design and a priced plan if it is not. The review is yours either way.