WHEN SOMETHING
HAS TO BE REPLACED.

Being built

A replacement is two movements and one commercial decision: something comes back, something goes out, and somebody decides who pays. Systems that model it as a single event lose the inventory on one side and the cost on the other.

GET STARTED →

What to know

Two movements, not one

The returned item is stock with a condition and a disposition — resell, repair, scrap. The replacement is an outbound shipment with its own cost. Netting them into "a replacement" makes both invisible.

Who pays is the actual question

A defect, a wrong item shipped and a change of mind are three different answers, and deciding the policy in advance is what stops each case becoming a negotiation the customer wins or loses on persistence.

The pattern matters more than the case

Individual replacements are noise. The same product replaced repeatedly is a quality signal, and it is only visible if the reason was recorded rather than the cost being absorbed.

Status

Designed, not built. Returns exist as records on GRAJ; a replacement flow that links the inbound and outbound movements and their cost does not.

Where to go next

REPAIR, RECORDED.

A repair that leaves no record is a repair that cannot be relied on by the next owner.

Read it

FIXING THINGS IS COMMERCE.

Repair keeps goods in use, produces a second margin on inventory already paid for, and is treated by most commerce systems as an absence of a sale.

Read it

RETURNS

In your account — sign in and it opens on your own figures.

Open