← All implementations
RESALE / OPERATIONSLive · private app

CustomerReturned

Know what a return is really worth.

customerreturned.com
Visit website ↗
CustomerReturned’s inventory dashboard with demo units, workflow stages, costs, and outcomes.
The inventory workbench, shown with fictional demonstration data.

CustomerReturned is built around the messy reality of returned inventory: missing units, repairs, parts, fees, refunds, and the difference between a seller’s claim and what arrived.

The problem

A manifest is a claim, not an inventory count. Reliable decisions require physical reconciliation and costs that follow each unit through every change in its story.

The implementation

The workbench connects receiving, inspection, repair, sales, and returns with integer-cent cost allocation, private photos, role boundaries, and an activity history.

  • Manifest import and physical unit reconciliation
  • Acquisition, repair, sale, and return cost tracking
  • Private photos, QR labels, roles, and audit history
01Preview a manifest02Receive physical units03Test and repair04Record sale or return
02 / ENGINEERING DECISIONS

Where the details matter.

01

A manifest is not received stock

Imported seller claims remain distinguishable from physically received units. Operators can resolve shortages and exceptions before relying on the inventory.

02

Money follows the unit

Acquisition, freight, parts, labor, selling fees and refunds are represented in integer cents. Cash recovered and trading result are separate calculations.

03

History survives an exception

Returns, voided transactions and disposal are part of the model. Private photos and role boundaries support the operational record.

03 / PACKAGES & CODE

Inside the implementation.

The inventory and accounting rules are purpose-built application code. No shared commerce or workflow package is being credited for these features.

APPLICATION EXCERPT

The cost basis follows the item

Purchase, freight, parts and labor contribute to the invested amount using integer cents.

app/Services/Accounting.phpPHP
$i->loadMissing(['costs', 'sales.refunds', 'disposals']);
$basis = $i->purchase_cents + $i->freight_cents;
$parts = (int) $i->costs->where('kind', 'parts')->sum('amount_cents');
$labor = (int) $i->costs->where('kind', 'labor')->sum('amount_cents');
$invested = $basis + $parts + $labor;
Application source excerpt · lines 42–46. Surrounding setup is omitted.
APPLICATION EXCERPT

One shared attribution component

The site keeps its own copyright. SiteCredit adds the standard BWD attribution after it, using isolated styles bundled with the application.

SiteCredit package ↗
resources/views/layout.blade.phpBlade
<x-site-credit />
Actual component call. The shared stylesheet is included separately in the application build.
04 / VERIFICATION & CURRENT SCOPE

What holds it together.

  • Receiving and accounting behavior are exercised with fictional inventory.
  • Private image and member boundaries are enforced by the application.
  • The public address leads to sign-in, not an open customer dashboard.
CURRENT RELEASE

A private operations application. Marketplace integrations and payment processing are outside this release.

KEEP EXPLORING

DRD Trailers

Designed, Developed and Hosted by Better Web Design and Development Services, LLC