Device Inventory Workflows¶
This guide explains how Reyder receives phones, records each IMEI, sells the correct units, and keeps the purchase order, sales order, delivery manifest, and customer invoice connected.
Choose a task instead of reading the site front to back.
New operator? Start with the 15-minute Quickstart
Follow the Quickstart for the normal receive → sell → scan → invoice flow. If Odoo itself is new to you, read Odoo Basics first; it takes about 5–10 minutes.
Open this guide from Odoo
Click the book / Guides / Guías button in the upper-right Odoo bar. You can also bookmark reyder-docs.pages.dev. Click or tap any screenshot to enlarge it.
| I need to… | Start here |
|---|---|
| Learn the Odoo screen and safe scanner routine | Odoo Basics |
| Complete my first guided receive-and-sell practice | Quickstart |
| Understand the complete process | Workflow Map |
| Receive a supplier shipment | Purchasing & Receiving |
| Decide between receiving scan modes | Single Scan vs. Batch Scan |
| Decide whether phones need Reyder QC | Quality Control & Selling As |
| Enter a customer order correctly | Sales Orders |
| Create or understand the customer invoice | Sales Order & Invoice Linkage |
| Scan the phones leaving the warehouse | Delivery Manifests |
| Process a returned phone | Phone Returns and RMA |
| Fix an error message | Troubleshooting |
The three documents people call a “manifest”¶
These are different things. Use the full name when speaking or asking for help.
| Name | What it is | What it controls |
|---|---|---|
| Supplier IMEI file/list | A CSV or Excel file sent by the supplier with exact IMEIs | Which IMEIs were supposed to be in the shipment |
| Receiving Manifest | The Odoo record connected to a purchase order | Which physical IMEIs Reyder actually received |
| Delivery Manifest | The Odoo record connected to a sales order | Which inventory IMEIs Reyder is shipping to the customer |
The supplier file is evidence. The two Odoo manifests are workflow records. Uploading a supplier file does not receive phones, and receiving phones does not sell them.
Five rules that prevent most mistakes¶
- Scan the physical phone in front of you. Do not copy an IMEI from chat or a spreadsheet when the physical unit is available.
- Use only one receiving mode. An exact supplier list uses Verify Supplier IMEI List. No supplier list uses Receive Without Supplier IMEI List.
- Enter the customer promise, not every known fact. A blank optional Color, Grade, or Lock means Any / not promised.
- Choose the honest Selling As basis. Supplier-grade phones sold immediately use As Received. Reyder's own verified promise uses Reyder QC Verified.
- Never create a duplicate invoice or sales order to fix scanning. Open the linked documents and correct the source record instead.
The normal everyday path¶
Purchase Order
→ Receiving Manifest
→ receive exact physical IMEIs
→ Sales Order
→ Delivery Manifest
→ Finish IMEI Scan review
→ Complete Delivery
→ linked Customer Invoice
For most wholesale sales, start with the sales order. The outbound scan confirms the order if necessary and assigns the exact inventory units. Complete Delivery, after the Finish IMEI Scan review, posts the shipment. Odoo then creates/posts the customer invoice, posts valid draft billing already linked to that SO, or invoices only a genuine uninvoiced remainder.
Use the invoice-first workflow only when customer payment must come before fulfillment.
Start by role¶
Read Purchasing & Receiving, then Single Scan vs. Batch Scan.
Read Sales Orders, then Sales Order & Invoice Linkage.
Read Delivery Manifests.
Use Quickstart, the End-to-End Walkthrough, and the User Handoff Guide.
What this documentation does not authorize¶
Documentation explains the intended workflow. It does not authorize someone to weaken a customer promise, bypass a manager control, alter a completed accounting document, or ship a rejected IMEI. Stop and ask a manager when the physical facts and Odoo disagree.