Four request types
Ship request, return only, return and replace, and advance replacement, each on one append-only timeline.
Products / Logistics & returns
Shipments, returns, replacements, and repairs on one lifecycle, with carrier-tracked legs, inspection with photos, and a public status page for customers.
Illustrative product preview. All records and counts are sample data.
Ship request, return only, return and replace, and advance replacement, each on one append-only timeline.
Restock, scrap, recycle, quarantine, or repair per item, with photos, reasons, serial numbers, and warranty.
FedEx, UPS, DHL, and USPS by verified webhooks. Blue Dart and Delhivery as tracking links.
From a draft, a customer email, or the API. Both legs of a return and replace are tracked side by side.
Outbound deliveries complete on the carrier scan. Inbound legs prompt your team, because a scan says the box arrived, not what is inside.
Per-item dispositions with photos. Repairs get their own tracked lifecycle back to the customer.
A public, no-login status page by request number and email. Mismatches return "not found".
On Logistics, the SLA Breach Predictor, Photo Inspection, and Return Forecast agents draft the next move. Manual receive, deliver, or cancel always wins over automation.
About Maya AIFour: ship request (outbound only), return only, return and replace (both legs tracked, complete only when both finish), and advance replacement, where the replacement ships before the return arrives.
FedEx, UPS, DHL and USPS through verified carrier webhooks. Blue Dart and Delhivery are supported as tracking deep links. Outbound deliveries complete on the carrier's delivery scan; inbound legs prompt your team instead.
Yes. A public status page lets a customer check progress with their request number and email. Mismatches return "not found", so requests cannot be enumerated.
Per-item dispositions of restock, scrap, recycle, quarantine or repair, with item photos, per-item reasons, serial numbers and editable warranty. Repairs get their own tracked lifecycle through to delivery back to the customer.
No. Manual receive, deliver, or cancel always wins and stops the tracker. Automatic transitions are logged as system actions, never as a fake user.
Yes. Logistics is sold as its own module. Run it alone or with Purchasing, Inventory, Vendors, and Production.
Arthiva is invite-only while we build with early customers. Logistics runs on its own or with the rest of the platform.