A Change Log Can Become a Small Logistics Service

Changing one address can affect different delivery cycles

In recurring delivery, changing an address is not simply editing one address field. Yuhan Corporation’s Beodeul Market (유한양행 버들장터) says on its recurring delivery management page that an address change made after automatic payment is complete and delivery preparation has begun will not apply to that cycle. The customer may have completed the change, but the item about to leave can still go to the old address.

Cafe24, a Korean e-commerce platform, divided recurring-delivery address changes in 2021 into “all,” “basic information,” and “scheduled delivery information.” According to the Cafe24 notice, changing only basic information does not apply to scheduled cycles that have already been created; a specific cycle must be changed separately. This is why a service needs to show not only what changed, but also which delivery cycle it applies to.

A missed handoff creates small costs and repeated work. In a November 26, 2024 customer post and company reply from High Street (하이스트릿), the company acknowledged that it had missed an address correction and said the delivery had already started, so the address could not be changed. The Korea Post redelivery charge for that individual order was KRW 4,800. It is not a figure for recurring-delivery losses overall.

Food-ingredient deliveries also have little time to accept changes. Jigu Food (지구농산), a food-ingredient supplier in western Gyeonggi Province, states in its delivery guide that orders close at 4 pm the previous day and are delivered the next dawn or morning. A quantity, address, or closure-date change after 4 pm means both the prepared loading list and the driver’s instructions must be updated.

One food-logistics operating case published by the Korean National Law Information Center (국가법령정보센터), a government legal-information service, describes checking each vehicle’s work start, departure from the center, arrival at the store, end of work, delay time, and reason for delay. This is an operating case from that company, not a requirement for every business. Still, it shows why recording the change and delay process—not just marking a delivery complete—helps explain what went wrong.

Start with a six-person food-ingredient supplier

Imagine a local food-ingredient supplier with six employees, two refrigerated vehicles, and 40 restaurant stops. In the morning, the owner receives a text saying, “Please remove two boxes for today.” An employee passes it into a KakaoTalk group chat. The office spreadsheet still has the original quantity, and the driver leaves with a sheet printed the day before.

Then come changes to closure days, receiving locations, empty insulated-bag collection, and returns for quality issues. As one request is copied two or three times across a customer chat, spreadsheet, loading sheet, and driver message, a delivery date or quantity can be missed. When the person in charge is off, the owner has to reconstruct from memory who replied and whether the driver was told.

This business does not need to be sold a large system that manages every vehicle location and warehouse inventory from day one. Start with a screen that gathers only what differs from the original schedule this week. An employee enters phone requests in one line. Text and KakaoTalk requests are copied in with the customer name, effective date, quantity, and whether collection is required.

When a change arrives, the service shows the original schedule and the revised schedule side by side. It moves to “confirmed” only after the customer, office, and driver have all confirmed it. If departure is near and the driver has not confirmed, it rises to the top of the first screen. Drivers see only the customer locations that changed today, not the full account list, on their phones.

After delivery, the business attaches delivered quantity, collected quantity, a photo, or the recipient’s name to the change record. It can then distinguish whether the customer changed too late, the office missed the handoff, or the driver confirmed but handled it differently. Redelivery and extra-visit charges can also sit on the same record as evidence for the next month’s settlement.

Much work still belongs to people. Someone must clarify an ambiguous phone request, decide whether to accommodate an urgent request from a long-standing restaurant customer, and judge damage or a quality problem in the field. This service is less a tool for making those decisions than a tool for making sure the decisions are passed on without omission.

Other companies can quickly copy the screens. But it takes months to learn which accounts often change after cutoff, how to notify each driver for the fastest confirmation, and what explanation helps customers accept an extra charge for an uncollected item. Once accounts and drivers begin using the same screen every day, customer-specific change data, relationships, trust, and access to customers become assets that are harder to copy later.

Elsewhere, change handling and proof have become separate products

Tomato Mountain Farm in the United States delivers weekly produce boxes to members in the Chicago area. It uploaded order files to OptimoRoute, which plans delivery routes, and started by fixing recurring delivery days by area—for example, Saturdays for the northwest. OptimoRoute charges monthly based on the number of drivers included in a plan, and its publicly listed annual Pro price is USD 44.10 per driver per month.

A supplier case study says membership grew from 300 to 1,200 over 30 days and delivery days expanded from two to four per week. The claim that efficiency improved by up to 300% comes from the supplier and customer, so it is not an independently verified result. The useful lesson is that they fixed recurring days by area before introducing more complex real-time dispatching.

Petal&Post in South Africa delivers flowers and gifts, including weekly, fortnightly, and monthly flower subscriptions. Previously, it organized orders in Google Docs, sent them to drivers through WhatsApp, and had drivers create their own sequences in maps. It later adopted Track-POD to bring delivery order, customer notifications, and electronic proof of delivery into one place.

The Petal&Post case study says the business handled ten times its usual order volume on Mother’s Day. Because this is a company’s own statement, the performance figure needs separate verification. Track-POD charges based on the number of drivers or vehicles and provides electronic proof of delivery and recurring routes. The central point in this case was not route finding, but having a completion record ready to show customers when they asked.

Veda Milk in India delivers milk and dairy products to households in Noida and Greater Noida. Customers can order daily, every other day, or on another chosen schedule, and can request a vacation pause or quantity change up to 12 hours before delivery. It separated customer, driver, and administrator screens to connect daily delivery lists with changes.

A developer announcement claims that 78% of existing customers used the screens six months after launch. This is not an independently verified figure, but it shows a direction in which customers directly pause or change the quantity for the next delivery cycle.

Four things you can build now

1. This week’s change inbox

• What it does: Attaches requests received through phone calls, text messages, and KakaoTalk to each customer’s recurring schedule, and records the effective cycle and the people who confirmed it.
• Who uses it: Office staff at local businesses with three to eight employees that regularly deliver water bottles or coffee beans.
• Why now: In recurring delivery, basic information and already-created cycles can be separate, so the product needs to show “from when this changes,” not merely “this changed.”
• First screen: Show only changes for today’s and tomorrow’s departures that drivers have not yet confirmed, as red cards.

2. A customer screen to confirm the next delivery

• What it does: Lets customers use one link to check and change the next delivery date, quantity, receiving location, and number of empty containers before the cutoff.
• Who uses it: Small food-ingredient suppliers serving dozens of daycare centers and restaurants whose weekly order quantities vary.
• Why now: Instead of having staff copy the same information from multiple chat windows, the supplier can have customers directly confirm the delivery cycle that will be affected.
• First screen: Under “Next delivery: September 3, morning,” show the current quantity, planned collection quantity, change cutoff time, and a confirmation button.

3. Today’s change cards for drivers

• What it does: Hides the usual schedule and shows only today’s changed addresses, quantities, collection requests, and the order in which to confirm them.
• Who uses it: Businesses with two to five drivers that deliver and collect laundry from hotels and beauty salons on set days.
• Why now: It reduces missed change handoffs without requiring drivers to learn an entirely new dispatch process.
• First screen: List accounts in driving order, distinguish address, quantity, and collection changes with color, and add “read” and “complete” buttons.

4. A log for returned items and extra costs

• What it does: Records containers sent to each account, containers returned, reasons for non-return, extra visits, and redelivery costs together.
• Who uses it: Side-dish and food-ingredient suppliers that collect reusable insulated bags or food containers on the next delivery.
• Why now: Photos and collection history are needed to distinguish driver responsibility, customer non-return, and damage, and to explain charges.
• First screen: Show “12 held by account · 8 collected today · 4 uncollected,” with a place to attach a reason and photo immediately.

What to check today

With permission from one recurring-delivery business owner, review the past seven days of text messages and KakaoTalk together for 30 minutes. For each change, write down only the sender, original schedule, new schedule, person who passed it on again, and proof of completion. If there are five or more changes in a week and at least two cases where the same information was passed to two or more people again, it is worth testing a “this week’s change inbox” before a large dispatch system.

Why this matters where you are

Korea’s specific conditions in this article include Korean e-commerce platform behavior, KakaoTalk-based work handoffs, local delivery cutoffs, and KRW-denominated redelivery costs. In your market, check whether recurring deliveries separate account changes from already-created delivery cycles, and where staff currently repeat the same change by hand. You can test a small confirmation and evidence workflow before replacing routing, inventory, or other larger operations systems.