Will-Call Notifications for Sage 100
When a pickup order’s status in Sage 100 says it’s ready, enrolled customers are told by text or email, by a person or on the schedule they chose. Will-call bins are aged, so what nobody picked up goes back to stock or back to the customer.
Dispatch & deliveryUpdated Oct 202620 ERPs
See it work on Sage 100.
Click through the steps. Fictional data, in Sage 100’s terms; the real thing runs on Sage 100.
| Order | Customer | Lines | Bin | Ready since | Enrolled |
|---|---|---|---|---|---|
| SO 88490 | Mill Creek Carpentry | 3 of 3 | W-4 | Today, 10:20 am | Text |
| SO 88482 | Shoreline Electric | 6 of 8, 2 on order | W-2 | Today, 9:05 am | |
| SO 88377 | Westfield Masonry | 2 of 2 | W-7 | 8 days | Not enrolled |
| SO 88301 | Ferry St Renovations | 1 of 1, special order | W-9 | 19 days | Text · 2 reminders sent |
Order status read from the ERP, bins and ages kept in Lunica. Who gets a notice depends on who enrolled.
The problem, as it happens in Sage 100.
A contractor orders by phone, the yard pulls it, the ticket goes in the will-call rack, and whether anyone calls depends on who pulled it. The order sits in Sage 100 as ready, the material sits in a bin with a name on it, and the customer calls at four to ask if it’s been pulled yet.
A will-call bin that nobody picks up becomes inventory nobody can sell. The 248SPF the count says is on hand is in a bin with someone’s name on it, the cycle count finds a variance, and the special-order door that sat there for six weeks goes back to the vendor with a restocking fee, or it doesn’t go back at all.
How it works.
- 1
Ready orders are noticed
When a pickup order in Sage 100 moves to picked, staged or ready, however your yard marks it, Lunica picks it up on the next read, with the customer, the lines and the bin or bay from the ticket.
- 2
The customer is told
Enrolled customers get a text or email: what’s ready, where to come, the hours, and the lines still on order if the pickup is partial. The counter sends it, or it goes on the schedule the customer chose when they enrolled.
- 3
Will-call is aged
Every ready order that hasn’t been picked up is listed by days in the bin, with the customer, the value and whether it’s stock or special order. A reminder is drafted at the age you set; a person sends it.
- 4
What nobody picked up is dealt with
Past the limit, the yard manager decides per order: back to stock, deliver it, or call the customer. Stock goes back on the shelf and the counter keys the order change in Sage 100; a special order is held or billed under the terms the customer signed.
How it connects to Sage 100.
Lunica reads open orders, their status and lines, the customer maintenance record and the customer’s pickup contact, and the item record for stock and special-order flags, through Sage 100’s ODBC driver, under a user that can only read. Enrolment, the schedule a customer chose and the bin ages are kept in Lunica.
Nothing is written to Sage 100 by Lunica and nothing is sent on its own. Notices go only to customers who enrolled, sent by a person or on the schedule they chose. When a will-call order is put back to stock or converted to a delivery, the order change is keyed by your team in Sage 100.
What a week looks like.
- Every ready pickup, the customer told the same hour, by text or email.
- Fewer calls to the counter asking if it’s been pulled.
- Will-call listed by age, with a reminder drafted for each.
- Bins back to stock on a decision, not when someone trips over them.
Questions
Does it text every customer?
No. Only customers who enrolled, by text or email as they chose. The counter sends the notice, or it goes on the schedule the customer picked when they enrolled.
How does it know the order is ready?
From the order status in Sage 100, whatever your yard already sets when a pickup is staged. If your yard doesn’t mark it, the counter marks the order ready in Lunica.
Does it write to Sage 100?
No. It reads order status and lines. Returning a bin to stock or converting a pickup to a delivery is keyed by your team.
What about partial pickups?
The notice lists what’s ready and what’s still on order, read from the lines. A second notice goes when the rest lands, to the same customer, never twice for the same lines.
How do customers enrol?
From the portal, from a link on the invoice email, or by the counter adding the number at the desk. They can stop any time by replying.
What counts as too old?
You set it: days in the bin, by stock or special order, by customer type. Past it, each order is a decision for the yard manager, not a rule that acts.
Does it need a server?
Lunica runs on one Windows server inside your network, beside the Sage 100 server, set up and maintained by Lunica. It reads Sage 100 through Sage 100’s ODBC driver, under a user that can only read. There is no inbound connection from outside your network.
What does Lunica read in Sage 100?
The customer maintenance record, open items and terms, purchase orders and receipts, the item record, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Sage 100?
Nothing lands in Sage 100 without a person. What belongs in Sage 100 goes back as a Sage 100 import or Visual Integrator job where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in Paperless Office. Lunica reads them when a workflow needs one and never writes to them.
The same workflow, on another ERP.
Will-Call Notifications is written for every system on the list. You’re reading the Sage 100 version.
See it on your Sage 100 data.
Thirty minutes. We walk the workflow on Sage 100 data, then map it to yours.