30-min call with RobBook a proof-of-concept call
Job 01 · Counter and accounting

// Heavy duty truck parts distributors · Core return credit checks

Core return credit checks, with each return read against the sale and the supplier's policy before credit goes out.

A shop drops off a worn compressor with a tag and a ticket number, and somebody has to work out what it is owed. First the return has to match the sale it came from and the policy of the supplier who charged you the core. In a free AI proof of concept, AI checks copies of 20 to 30 returns your counter already closed. Your reviewer, the person who knows your core returns best, compares each list of differences with what your team found.

Book a proof-of-concept call30 minutes with Rob
Closed returns
20 to 30
Credits issued
None
Cores ruled on
None

// The one job

From a tag and a worn part to a list of what doesn't match

A core comes back with whatever paper the customer kept: a return tag, the old ticket, a number written on the box, sometimes nothing. Your counter hunts down the sale, someone checks that it is the right core and that it came back in time, the old part goes on the shelf for the supplier, and accounting credits the customer. The supplier decides later whether you get your own core charge back.

For the test, AI reads copies of those records and produces a check sheet for each return: the invoice number, the part and core numbers as each document wrote them, the ship date and return date, the policy's condition and time-limit terms with the clause quoted, and every place the paper disagrees. It issues nothing and rules on nothing. Your reviewer sets each sheet beside what your counter and accounting actually did.

Core return tagFrom the counter
Invoice no.
Part no.
Core no.
Returned on
As writtenQtyNoted at counter
Illustration, not a real tag
Read against
sale and policy
Check sheetDraft
Sale found
Days since invoice
Policy clause
Held for
FieldOn the saleOn the return
Made-up sheet, for illustration

// What makes it hard

Why a returned core can't be credited from the tag alone

The clock starts and stops in different places. One supplier's core policy for remanufactured components takes a core back for 90 days, adds a handling fee after day 45 and gives no credit after day 90, and it tells customers that a tracked shipment is the record of the return date. A second supplier's core return guidelines count 60 days from the invoice date and want the core received by then, so the day you ship it doesn't settle it. Your own terms to the customer may run on yet another calendar. Each check sheet shows the invoice, ship and received dates as written and names the count each policy uses.

The number that decides is often not the number on the part. That second supplier only takes cores in the same group or core code classification as the exchange unit ordered, which it lists in a core acceptance catalog, and its packing list can identify a core by code or group, by part number, or by invoice or order number. The first asks for like-for-like or style-for-style returns. A core that fit the truck can still be the wrong core on paper. The sheet carries the part number from the invoice, the core number from the tag and the group from the policy, each as written, and treats no two numbers as the same part on its own.

Missing paper can move the credit. Without an invoice or order number on the packing slip, the second supplier applies credit to the oldest outstanding invoice with the matching exchange unit, which may not be the sale you're crediting. It pays only for cores owed, won't bank extras, and gives you 10 days to answer a discrepancy notice. The first says no packing slip in the box means no refund, and has every return started online by order number and email. A public customer may add a rule of its own: Ocean County, New Jersey's parts scope for vehicles under 15,000 GVWR has core charges shown on every quote and purchase order, credit issued once the core is back, and a written explanation when one is turned down. The sheet names each missing document and quotes what that party's terms say happens next.

Condition terms are written for an inspector. Both suppliers refuse cores hurt by non-operational causes such as rough handling, fire, bad removal or poor storage. The first accepts weather rust on exterior surfaces, only light flash rust on interior surfaces and machined areas, and no assembly built from mismatched parts, and it wants fluids drained and the new unit's plugs and caps fitted to the core. The second wants cores in off-engine condition, complete and never taken apart since removal, won't take electronic injectors with broken stator terminals unless its catalog says so, and turns down broken nozzle tips on certain injector series. Warranty returns are different paper again: one maker's guide for reman air dryers, calipers, compressors and water pumps denies a return at the counter when its date code is missing, unreadable or altered, and that code can be month and year or day of the year and year. The sheet quotes those terms beside what your counter wrote down, and a person decides.

Tax can follow the core, and your reviewer will check for it. A Kansas opinion letter from 2000 treats the core charge as part of the taxable selling price and tells the retailer to refund the charge and the tax on it when the part is turned in. Colorado's August 2017 general information letter, which by its terms doesn't bind the department, treats the charge as part of the purchase price, says it isn't a security deposit, and finds a refund of tax inappropriate. Michigan excludes core credits from sales price from January 1, 2017 where the charge is a recycling, deposit or disposal fee stated separately on the invoice. So the sheet shows tax on the core line and tax on the credit and leaves the answer to accounting. Nothing here is legal or tax advice. Your reviewer checks that the right sale was found, that every mismatch is real, that a core credited once isn't credited twice, and that any return the sheet couldn't tie down was held.

// What you send

Returns your counter has already closed

Copies only
Several suppliers
01

20 to 30 closed returns

Cores your counter credited or turned down in the last few months, from several suppliers and branches. Include one that came back late, one with a wrong number on the tag and one a supplier refused.

02

The sale behind each one

The invoice or counter ticket that charged the core, the return tag or form, and the packing slip or shipping paper that went with it to the supplier.

03

Each supplier's written policy

The core policy or guidelines in force on those dates, plus any core acceptance catalog. If a supplier's terms changed partway through, send both versions.

04

What happened afterward

The credit memo to your customer and the supplier's credit or rejection, where you have them. Scans and exports are enough once the NDA is signed. Nobody signs in to your parts system or a supplier's portal.

// Before it starts

Settled before a tag is copied

The owner puts each of these in writing first.

Terms for the core return testOwner signs off
Your reviewer
Named by the owner, often the parts manager or whoever posts core credits
Success criteria
In writing: which mismatches must be caught, and how a held return is scored
Suppliers
Your reviewer's pick, usually the ones sending the most cores
Who decides
Your counter and accounting: every credit and every core's condition
Price
A range for running it live, quoted before a tag moves
NDA
Signed before the first copy

// How the test is judged

Your team's call beside each check sheet

Return by return
against the credit that was issued
Across the same 20 to 30 returnsWhat your team didDraft check sheet
Invoice number, and the right sale foundFilled in on your returnsFilled in on your returns
Part and core numbers, as each document wrote themFilled in on your returnsFilled in on your returns
Invoice, ship and return dates, with the policy's countFilled in on your returnsFilled in on your returns
Condition terms quoted from the policy in forceFilled in on your returnsFilled in on your returns
Missing documents namedFilled in on your returnsFilled in on your returns
Mismatches your team caught, and any inventedFilled in on your returnsFilled in on your returns
Returns held for a person, with the reasonFilled in on your returnsFilled in on your returns
Blank for now. Every cell waits for your own closed returns to go through.Your reviewer fills the columns and makes the call.

// After a yes

About 30 days on returns as they come in

With your reviewer's yes, new core returns get the same check sheet for about 30 days.

A person at your counter or in accounting reads every sheet and resolves each mismatch before any credit reaches a customer. Credits post the way they do today.

Any further job is a separate decision at a separate price.

// Later, one at a time

What could come after core checks

Possibilities, not promises
Each priced alone
  1. 01

    Fleet parts bid sheets

    A public buyer's parts solicitation read into a draft price sheet for your inside salesperson to fill and approve.

    Next
  2. 02

    Supplier credit follow-up

    Cores shipped back matched to the supplier's credit memos, with any still unpaid listed for accounting.

    Then
  3. 03

    Price book changes on contract accounts

    A new supplier price book compared with every contract that names it, for your pricing lead to act on.

    After that

// One hard limit

It never issues a credit or decides whether a core is acceptable.

The proof of concept never touches your parts system, a live order or a live credit. It reads copies of closed returns and writes its sheet for your reviewer. A person issues every credit and makes every call on a core's condition, and the AI contacts no customer and no supplier.

Priced per job. You get a range before the proof of concept and a fixed price before you sign.

Rob sets the range on the call from two counts: cores coming back across your counters in a month and how many suppliers' policies apply.

// Questions

Questions about checking core returns

Will the AI decide whether a core is acceptable?
No. Condition belongs to your counter and to the supplier's inspection. The sheet quotes the policy's condition terms next to whatever your counter wrote down, and a person makes the call.
Who gets the list of mismatches?
A person at your counter or in accounting, whichever the owner names. During the test only your reviewer sees it, and no customer or supplier hears from us.
Some customers bring cores back with no paperwork. Can it still check those?
It looks for the sale using whatever is on the tag and says so when it can't be sure. A return with no match goes on the list and is never credited on a guess.
Does this cover warranty returns?
Not in this test. A failed part sent back under warranty follows different rules and would be a separate job. The sheet only marks a return that looks like a warranty claim so a person can route it.
What if a supplier's core policy isn't in writing?
Your reviewer writes down the rule your team follows before the test begins, and the check runs against that. Where no rule exists at all, the return is held instead of checked.
Rob Eason

Rob Eason, founder

// Book a proof of concept call

Bring a month of credited cores.

A 30-minute call with Rob covering your branches, your role, the suppliers you send the most cores to and roughly how many come back in a month. Tags, tickets and policies stay with you until the NDA is signed.

  • Co-owned a 60-employee financial services firm and sold his share to his partner.
  • Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
  • 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
  • 4.3/5 from 6 Google reviews of Massmarket AI.
  • Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
  • Takes every proof-of-concept call himself.