For furniture, whitegoods, building and landscape suppliers

Delivery Booking and Bulky Goods Integration

For most online retailers, dispatch is a label and a tracking number. For anyone selling lounges, fridges, spas, flooring or a pallet of pavers, dispatch is a slot on a particular truck, on a particular day, with two people and possibly a tail lift. What you are selling at checkout is not just the product. It is a piece of delivery capacity you may not have.

This page covers how to make that capacity visible and sellable: zone and access rules that reflect the real cost of getting to a suburb, slot booking that holds and then confirms, orders that split between parcel and bulky freight, installation jobs scheduled alongside the delivery, and the proof, communication and reconciliation that stop failed deliveries eating the margin.

Book a Delivery Systems Call (03) 9003 0111

What You Are Really Selling

2 scarce things

The stock and the truck

Checking only one of them at checkout is why delivery dates slip

Zones, not distance

How bulky freight is actually priced

Postcode zone tables in AUD, with honest surcharges for remote runs

Failed delivery

The most expensive event in the process

A redelivery costs the margin on the order and a support conversation on top

1 access question

Stairs, lift, frontage, gate width

Asked at checkout it is a field, asked at the door it is a return

Four Things Bulky Delivery Does Not Forgive

Parcel logic applied to furniture produces the same four problems in every business we look at.

Delivery capacity has to be modelled, not assumed

A run has a finite number of drops, a finite volume, and a crew who cannot be in two suburbs at once. If the website sells nine deliveries into a zone that takes six, someone spends Monday morning ringing customers to move dates. Capacity needs to be expressed in whatever unit genuinely constrains you, drops, cubic metres or crew minutes, per zone per day, and the checkout needs to consume it in real time rather than letting dispatch find out later.

Australian geography makes zones unavoidable

The cost of getting a lounge to an inner suburb, an outer growth corridor, a regional town and a property past the end of the bitumen are four different numbers, and averaging them means subsidising the long runs with the short ones until the mix changes. Zone tables by postcode, with explicit surcharges for remote runs, island and ferry destinations and anything needing a line haul plus a local agent, are the only honest basis for both the price and the date.

The crew and the equipment are part of the product

A one person delivery to a kerb is a different service from two people carrying a fridge up a flight of stairs, which is different again from a crane truck placing a spa over a fence. Each has a cost, a duration and a set of preconditions. Selling them as one flat delivery fee means either overcharging the easy jobs or losing money on the hard ones, and it leaves the driver to negotiate on the doorstep, which is the worst possible place to have that conversation.

Mixed orders need a policy, not a guess

A customer buys a bed frame, a mattress and two cushions. The cushions go by parcel carrier tomorrow, the bed goes on a truck next Tuesday, and the mattress is coming from the supplier the week after. Do you ship as available, hold everything until one delivery, or split and tell the customer clearly what arrives when. There is no universally right answer, but there is a wrong one, which is deciding it per order at the pack bench.

Six Parts of a Connected Delivery Operation

Slot booking is the visible part. These are the pieces that make it hold up once real volume arrives.

Date confirmed

Capacity and slot booking

Available dates published per postcode based on remaining capacity, the service level the order requires and the lead time to get stock to the right depot. The slot is held while the customer completes checkout, released automatically if they abandon, and confirmed on payment. The result is a date the customer chose and the operation can actually honour.

Priced right

Zone and access rules

Postcode zone tables driving both price and available service, with access questions asked at checkout: stairs and how many, lift access, driveway and frontage, gate widths for landscape supplies, whether someone will be home and who can sign. Captured once, printed on the run sheet, and visible to the crew before they load rather than when they arrive.

Clear promises

Split and consolidation logic

Order lines assigned to the right method automatically, parcel for the small items, bulky freight for the rest, with a documented rule for what happens when one line is delayed. Customers are told what arrives when, in one message, rather than receiving three tracking emails and concluding that something has gone wrong.

Live status

Run sheets and driver updates

Runs built from confirmed bookings, sequenced sensibly, and pushed to the driver or the contract carrier with the access notes attached. Status comes back the same way: departed, on the way with an estimated window, delivered with a photo or signature, or attempted with a reason. That status flows straight to the customer and the support desk, which removes most of the where is my delivery calls.

Job booked

Installation and trades

Where the delivery is followed by connection, assembly or installation, the job is scheduled as part of the same booking rather than as a second phone call, including whether a licensed trade is required and what paperwork has to come back. For appliances and anything plumbed or wired, the certificate and the sign off belong in the order record, not in a folder in the van.

Invoices checked

Freight reconciliation

Carrier invoices matched against the bookings actually delivered, including the extras that get added quietly: waiting time, second attempt, tail lift, futile delivery, remote surcharge. Nobody checks these by hand at volume, which is exactly why they need checking automatically. The differences are usually small individually and meaningful annually.

The Delivery Process, Before and After

Task	Traditional	Capacity Aware	Notes
Choosing a delivery date	Guessed, then confirmed by phone	Chosen from real capacity	Removes the call that currently happens for every single bulky order.
Pricing a regional delivery	Flat fee, occasionally a loss	Zone table with surcharges	Surcharges are easier to accept when they are shown before payment rather than added after.
Knowing about the stairs	Discovered on arrival	Asked at checkout	Access data also lets you price a two person service where it is genuinely needed.
Mixed parcel and bulky order	Held until everything is ready	Split by rule, explained once	A clear single message beats three tracking emails that look like a mistake.
The day before	Customer hopes someone rings	Window sent automatically	The single cheapest change available, and it cuts failed deliveries immediately.
Proof of delivery	A signature on paper, in the van	Photo and time on the order	Settles damage and non delivery claims quickly, which matters most with high value goods.
Failed delivery	Rebooked manually, cost absorbed	Reason captured, fee applied by rule	Fees must be disclosed up front to be fair and enforceable, so put them in the terms shown at checkout.
Carrier invoice	Approved because checking is impossible	Matched to delivered bookings	Waiting time and futile delivery charges are where the unexplained variance usually lives.

Where Bulky Delivery Integrations Come Unstuck

Selling a date the operation cannot honour

The failure that damages trust fastest, because the customer has organised their day around it. Slots must be reserved when selected and released on a timer if checkout is abandoned, capacity has to reflect crews and vehicles actually rostered rather than a theoretical maximum, and the model needs to know how long stock takes to reach the depot serving that postcode. If capacity data is genuinely unavailable, publish a conservative range rather than a specific day you are guessing at.

Delivery promises that mislead

Under Australian Consumer Law, statements about when goods will arrive are representations, and a business that routinely misses its published timeframes is exposed regardless of what the fine print says. Consumer guarantees also apply to delivery itself, and the goods remain your responsibility until the customer receives them. Practically: publish dates you can meet, notify promptly when something slips, and keep records of what was promised. Systems that record the promise and the outcome make this straightforward rather than stressful.

Access information nobody sees

Capturing whether there are stairs is only half the job. If the answer does not reach the run sheet, the crew and the vehicle allocation, it may as well not have been asked. Access notes should drive service selection, appear on the driver’s screen before loading, and trigger a call to the customer where the answers are contradictory. A futile delivery because a truck could not fit down a driveway is a cost you paid to collect information you already had.

Contract carriers outside the system

Many Australian bulky deliveries are performed by subcontracted crews and regional agents who will not log into your platform. That is workable, but it needs a deliberate design: a simple mobile view or a structured file exchange, agreed status codes, and a rule for what happens when status never arrives. The worst outcome is a delivery network you cannot see, where the customer is the first to tell you something went wrong.

Returns treated as a parcel problem

Getting a two metre lounge back is not a satchel and a label. You need a pickup booking with capacity of its own, a decision about whether the item comes back to the warehouse or goes straight to a seconds channel, and clarity about who pays. Where there is a major failure under Australian Consumer Law, the supplier generally bears the cost of returning goods that are too large to post, so a policy that assumes the customer will arrange transport will not survive contact with a dispute.

Building a scheduling platform you do not need

If you do a handful of bulky deliveries a week from a single depot with one van, a shared calendar and a good booking form will serve you better than capacity modelling. The case for real integration appears with multiple vehicles, multiple depots, subcontracted crews, installation jobs or enough volume that Monday morning is spent rescheduling. We will tell you which of those you actually have, and where a simpler change would get most of the benefit.

How Yes AI Approaches Delivery Integration

A ride along before a design

We look at a real run, including the drop that goes wrong, and we sit with whoever currently books the dates. The constraints in this work are physical and local, and they do not show up in a requirements document.

Capacity modelled in your real units

Drops for some businesses, cubic metres for others, crew minutes where installation dominates. We use the unit that actually limits you rather than the one that is easiest to calculate, because the wrong unit produces a calendar nobody trusts.

Built, hosted and monitored by us

The integration runs on a managed cloud automation layer we operate, with record level logging and same day alerting. Peak periods and end of financial year sales are when this matters, so we load test before them rather than during.

Rules and terms that hold up

Access questions, surcharge tables, failed delivery fees and notification timing documented and reflected in the terms shown at checkout, so the commercial position and the system behaviour match. Your legal adviser checks the wording, we make the system honour it.

From Phone Booked Dates to a Connected Run

Five steps. Live slot booking on one depot and one zone set is usually running in five to eight weeks.

Map zones, services and capacity

Postcode zones, service levels, vehicles and crews, depots and the lead time to move stock between them. We also price a few real jobs properly to test the zone table against reality.

Agree the promise rules

How dates are calculated, how slots are held and released, what access questions are asked, and how mixed orders split. Written down and checked by dispatch before build.

Design the driver and carrier loop

Run sheets out, status back, proof of delivery captured, and a rule for missing status. Subcontracted crews are designed for explicitly rather than hoped for.

Build and pilot on one depot

One depot, one zone set, real bookings, with the manual process still available. We watch the first fortnight of run sheets and tune capacity against what the crews actually achieve.

Extend and reconcile

Remaining depots and zones, then installation scheduling and carrier invoice matching. Monitoring, documentation and a pre peak review each season.

FAQ

Can our website really show available delivery dates?

Yes, provided two things are true. You can express your delivery capacity in a unit that reflects what limits you, usually drops per run, cubic metres per vehicle or crew minutes per day, and you know how long stock takes to reach the depot that serves the customer’s postcode. With those in place the checkout can offer genuine dates, hold the chosen slot while the customer pays, and release it automatically if they abandon. Where capacity data is genuinely unavailable, the honest fallback is a conservative date range plus a confirmation, which is still a considerable improvement on a phone call the next day.

How should we handle regional and remote delivery pricing?

With a postcode zone table that you maintain deliberately, not with a flat national fee. Zones let you reflect the real cost of metropolitan, outer suburban, regional and remote runs, and to identify the destinations that need a line haul plus a local agent, a ferry, or a service you simply do not offer. Show surcharges before payment rather than adding them afterwards, since a disclosed surcharge is usually accepted and an unexpected one becomes a dispute. Review the table annually against actual carrier invoices, because the mix of where you deliver moves over time.

What access questions are worth asking at checkout?

Enough to select the right service and avoid a futile trip, and no more than a customer will patiently answer. In practice that is usually: stairs and roughly how many, lift access for apartments, whether a truck can get to the frontage, gate or side access width for landscape and building supplies, whether someone will be home, and any parking restriction. For very large items, a question about the doorway or lift dimensions saves the most expensive kind of failure. The important part is that the answers travel to the run sheet and influence vehicle and crew allocation rather than sitting in a field nobody reads.

Should mixed orders ship as available or as one delivery?

Pick a default and make it explicit, then allow exceptions. Shipping as available gets the customer their cushions tomorrow and costs you two freight movements. Holding everything gives one delivery and a longer wait, which is often fine for a bedroom suite and not fine for an accessory the customer needs now. Many Australian retailers default to splitting parcel from bulky, holding bulky lines together where the wait is short, and telling the customer clearly in one message what arrives when. What matters more than the choice is that it is a rule in the system rather than a decision made at the pack bench.

How do we bring subcontracted delivery crews into the system?

Deliberately and simply. Most contract crews and regional agents will not adopt your platform, so the practical options are a lightweight mobile view they can open from a link, or a structured file exchange with agreed status codes and timing. Either way you need three things: the access notes reaching the crew before they load, status and proof of delivery coming back in a form you can attach to the order, and a rule for what happens when status does not arrive at all. That last one is what keeps a subcontracted network visible rather than a black box.

Can we charge a fee for a failed delivery?

Commercially it is common, and fairness matters more than the number. A fee that is clearly disclosed before purchase, proportionate to the cost you actually incur, and applied only where the failure was genuinely outside your control is a reasonable position. A fee buried in terms nobody saw, applied when the crew arrived outside the promised window, is the kind of term that attracts attention under the unfair contract terms provisions. Systems help by recording exactly what happened: the window promised, the arrival time, the reason recorded by the driver and the photo taken at the door.

What does this cost to build and to run?

A first live implementation covering one depot, a zone table and checkout slot booking is typically five to eight weeks, with driver status, installation scheduling and carrier invoice matching added in later phases. Ongoing cost matters here because carriers change their surcharges and their file formats regularly, and your zone table needs annual attention. Across integration work of this kind, ongoing hosting, monitoring and support tends to run roughly twenty to forty percent of the initial build over time. We quote a fixed build price plus a flat monthly managed fee, and we avoid per delivery pricing because it punishes a strong trading month.

Sell the Delivery You Can Actually Make

Book a call. We will look at your zones, vehicles and depots, tell you what to automate first, and give you a priced plan.