Blanket orders that release for a year, bins you fill at the customer’s plant, and part numbers that mean something different to every buyer. Elixir keeps the cross-references, the counts and the contracts straight.
Releases are scheduled against the agreement, priced at the contract, and the customer’s remaining balance is a line in their file.
Vendor-managed bins and vending machines report consumption; replenishment is proposed from it, with the slow bins flagged before they become write-offs.
Customer numbers, vendor numbers, superseded numbers and your own. The counter types any of them and gets the right part and the contract price.
Six things that happen every week, and what Elixir does with each.
Agreements with a schedule, a price and a balance, released on time and reconciled at the end without a spreadsheet.
Consumption read from bins and machines, replenishment proposed, and the account’s real usage compared with what the contract assumed.
Customer, vendor, superseded and internal part numbers resolve to one item, at the counter and on the incoming PO.
Contract prices tied to cost with their review dates, so a cost increase becomes a conversation on the right day.
Items with no sale in a year, by bin and by dollar, with the vendor return window and the last customer who bought them.
Kits held as their components for stock and as one line for the customer, so the count is right and the invoice is simple.
A first pass is built from your sales and purchase history in days, because most cross-references are already implied by what you bought and sold together. The rest are confirmed as they are used.
Most machine and bin programs export consumption; Elixir reads those files or feeds and treats them like any other demand signal.
If you want. Many branches start by giving the rep the number; a customer page with releases and balances comes later.
Each contract carries its formula and review date. When vendor cost moves, the note says which accounts are affected and what the clause allows.
Every trade runs on different numbers, so there is a page for each.
Tell us what you distribute, how many branches you run and which systems you run them on. We reply within one business day and tell you plainly whether we can help.