Device Inventory¶

The operating system for Reyder Enterprises' mobile-device business. Tracks every device by IMEI from the moment it arrives on a supplier shipment through QC, sale, delivery, and financial settlement with the device owner.

First time here?

Start with the User Handoff Guide if you are training a team, or Quickstart if you are a single user learning your role. Use End-to-End Walkthrough for the full supplier-to-paid example.

Home dashboard

What this system does for you¶

Track every device individually. Each phone has its own IMEI, grade, battery health, storage size, color, and lock status. No guessing which unit is which.
Automate the paperwork that follows a sale. One sales order generates a delivery manifest, a packing box, a customer invoice, a vendor bill for Axis Mobile, and two settlement reports — all linked together.
Keep Axis Mobile's view clean. Axis owns the devices; Reyder sells them. The system gives Axis owner-side reconciliation totals while keeping Reyder's customer names, sale prices, sale dates, and SO numbers out of owner reports.
Support a warehouse you can scan through. Barcode flows for receiving, picking, packing, and task completion — one scan per action, with locking that prevents two people from claiming the same device.

The companies¶

Two companies share this database.

Company	Role	What they see
Reyder Enterprises	Operator + seller. Runs the warehouse, handles all POs and customer invoices, owns the day-to-day.	Everything.
Axis Mobile	Device owner. Consigns phones to Reyder for sale.	Only their devices and their owner-side settlement reports — no Reyder customer data.

This split is enforced by Odoo record rules, not by convention. See Security & Multi-Company for how that works and how to verify it.

The flow, from shipment to paid¶

 Supplier
    │ ships devices
    ▼
┌─────────────┐
│  Receiving  │  scan IMEIs, post GL (DR Valuation / CR GRNI)
└─────┬───────┘
      │
      ▼
┌─────────────┐
│     QC      │  grade, check battery + carrier, clear for sale
└─────┬───────┘
      │
      ▼
┌─────────────┐
│ Allocation  │  pin IMEIs to a sales order line
└─────┬───────┘
      │ confirm SO
      ▼
┌──────────────────────┐
│  Pick / Pack / Ship  │  barcode through Packing Box
└─────┬────────────────┘
      │
      ▼
┌─────────────────────────────────┐
│  Invoice + Settlement Reports   │  customer invoice, vendor bill to Axis,
│                                 │  paired Owner + Consignee reports
└─────┬───────────────────────────┘
      │
      ▼
┌─────────────┐
│    Paid     │  match vendor bill, mark report as Paid
└─────────────┘

Each arrow is automatic — the system handles the handoff when you complete the step before it.

Start here by role¶

If you are…	Start with
Training a team	User Handoff Guide
Learning the whole flow	End-to-End Walkthrough
A warehouse team member	Quickstart → Warehouse track
Sales ops	Quickstart → Sales track
Accounting / Finance	Quickstart → Accounting track
Setting up a new install	Setup & Configuration
Trying to debug something	Troubleshooting
Supporting production users	Admin Support Runbook

Daily workflows¶

The detailed how-to guides for each part of the system.

User Handoff Guide — training plan, role checklists, production readiness
End-to-End Walkthrough — one complete supplier-to-paid scenario
Purchasing & Receiving — PO creation, IMEI manifest scanning, receiving GL entries, and the narrow Device Intake shortcut for one-off company-owned devices
Quality Control — QC handoff, grading, M360 diagnostic checks
Consignment Agreements — setting up the Reyder ↔ Axis relationship
Sales Orders — creating orders, allocating specific IMEIs to lines
Delivery Manifests — picking, packing, marking shipments complete
Settlement Reports — owner vs. consignee split, vendor billing, marking paid
Retail Operations — retail reservations, retail sales, CSV import
Warehouse Operations — tasks, packing boxes, movement history
Inter-Company Transfers — moving stock between Reyder and Axis warehouses

Reference¶

When you need to look something up.

Accounting Reference — every GL entry the system posts, with conditions and examples
Device Lifecycle — every state a device can be in, and how it moves
Security & Multi-Company — record rules, data separation, testing isolation
Troubleshooting — common errors with fixes
Admin Support Runbook — shell-only recovery, deployment smoke checks, support escalation tasks

Glossary¶

Terms that come up repeatedly. If you see one of these in a guide and don't know it, check here first.

Term	What it means
IMEI	The 15-digit serial number stamped on every phone. Used as the unique ID for every device throughout the system.
Consignment	Axis owns the phones; Reyder sells them. Ownership transfers at the moment of sale, not before.
Manifest	A document listing IMEIs. A receiving manifest = what you got from a supplier. A delivery manifest = what you're shipping to a customer.
Grade	A physical-condition rating: Excellent, Good, Fair, Poor. Set during QC.
Settlement Report	The financial reconciliation after a sale. Generated in pairs: owner (goes to Axis) and consignee (stays with Reyder).
Commission	Reyder's cut of each sale. Defined on the consignment agreement as a flat amount or a percentage of sale price.
QC Handoff	The wizard that moves a batch of received devices from "just arrived" to "ready to sell," with grades assigned.
M360	Third-party IMEI verification service — tells you lock status, blacklist, carrier. Integrated into QC.
COGS	Cost of Goods Sold. The accounting entry that moves a device's value from stock (asset) to expense when it's sold.
Valuation account / GRNI	Stock valuation holds the inventory's asset value. GRNI (Goods Received Not Invoiced) is the liability until the supplier bill arrives.
Packing Box	The physical box devices go in for shipment. Scan-driven: one scan per IMEI packs it into the box and picks it on the delivery manifest.
Device Intake	A manual wizard for one-off company-owned devices with no PO or vendor manifest. Normal supplier and consignment batches should use IMEI Manifests instead.