Adding/Editing Device Models & Pricing Updates
Purpose: For Pricing Team, Tech Team, Vendor Ops, Operations & Management
1. Purpose of This Module
To ensure:
✔ Accurate and up-to-date pricing for all devices
✔ Smooth addition of new models & variants
✔ Correct deduction logic for conditions and issues
✔ Vendors get the right prices during inspection
✔ Customers get transparent & trustworthy pricing
✔ Ops & Sales teams avoid mismatching models
✔ Market-competitive pricing updated regularly
2. Who Is Responsible?
Primary Owner: Pricing Team (Mohsin Surya)
Supported By:
Tech Team → For implementation
Vendor Ops → For vendor device support mapping
CX → Reporting customer price mismatch issues
Ops → Reporting inspection-related errors
Management → Final approval for major pricing resets
3. Where This Module Is Located in Admin Panel
Admin Panel → Models & Pricing
This section includes:
Brands
Models
Variants
Storage options
Base prices
Deduction logic
Model images
Supported device types (Phone, Laptop, Tablet, Mac)
4. Adding a New Device Model (Step-by-Step)
Whenever a new device is launched OR not available in the system:
Step 1 — Create Brand Entry (If Required)
If brand doesn’t exist:
Go to Brands → Add Brand
Upload brand icon/logo
Save
Step 2 — Add Model Under the Brand
Go to Models → Add New Model
Select Brand
Enter Model Name (e.g., iPhone 16 Pro Max)
Select Device Type (Phone/Laptop/Tablet/Mac)
Upload Model Images
Save
Step 3 — Add Variants
For phones/tablets/macbooks:
Add storage variants
Add RAM options if applicable
Add processor variants for laptops
Add year model for Macs
Example:
iPhone 16 → 128GB / 256GB / 512GB / 1TB
Step 4 — Set Base Prices
Base price = price for “Like New / No issues / Perfect condition”.
Pricing inputs come from:
Market trends
Competitor prices
Recycle industry rates
Internal profit margins
Vendor purchase pricing
Mohsin sets the final base value.
Step 5 — Add Deduction Logic
Deduction logic is CRITICAL.
Based on:
Condition (Good/Fair/Bad)
Screen condition
Battery health
Body dents
Replacement parts
Non-working features
Storage, RAM, generation
Example deduction:
Battery health < 80% → -₹500
Screen replacement → -₹1500
Back glass cracked → -₹700
Step 6 — Final Testing
Tech team tests:
✔ Model shows correctly in app/website
✔ Price calculator works as expected
✔ Deductions apply properly
✔ Variants visible
✔ Images load smoothly
Step 7 — Publish
Once approved → Pricing goes LIVE.
5. Editing Existing Models or Updating Pricing
Pricing updates are needed when:
Market price fluctuates
High-demand models drop in resale value
New price trends observed
Competitors change their price
Hardware availability changes
Seasonal demand shifts
Excess vendor complaints for lower/incorrect prices
Step-by-Step:
Step 1 — Open the Model
Admin Panel → Models → Search Model
Step 2 — Update Base Price
Enter new value.
Step 3 — Update Deduction Pricing
Modify deduction slabs based on:
Screen crack impact
Battery health
Functional issues
Fair/Good/Like-New multipliers
Step 4 — Update Market Notes (Optional)
Useful for Ops/CX for internal explanation.
Step 5 — Save Changes & Notify Teams
Teams informed:
Ops
CX
Vendor Ops
Marketing (only if needed)
This avoids miscommunication.
6. Pricing Approval Workflow
Step | Team | Action |
|---|---|---|
1 | Pricing (Mohsin) | Draft pricing update |
2 | Management | Approves major changes |
3 | Tech | Implements change |
4 | Vendor Ops | Validates real-world impact |
5 | Ops | Confirms no user disruption |
6 | CX | Updated info for customer handling |
7. When a Pincode/Area Reports Incorrect Pricing
CX must:
Log the complaint
Attach screenshots or customer remarks
Notify Mohsin
Pricing verifies
If genuine → Update pricing
Communicate back to teams
8. BD & Vendor Ops Responsibilities in This Module
BD Team Responsibilities:
Track device pricing trends area-wise
Monitor high-value device performance
Ensure models are available in fast-moving cities
Share demand patterns with Pricing Team
Vendor Ops Responsibilities:
Ensure vendors support all newly added models
Train vendors on updated pricing
Report deduction issues from the field
Flag models causing frequent disputes
9. Common Scenarios & Solutions
A. New Model Not Showing in App
Cause: Tech sync issue
Solution: Clear cache, sync database, check variants
B. Wrong Price Showing
Cause: Incorrect deduction logic
Solution: Update rule under “Deductions”
C. Vendors Complaining About Too Low Pricing
Cause: Market fluctuations not synced
Solution: Review current market price & adjust
D. Customer Says Price Too Low
Solution:
CX explains condition-based pricing
Refer to deductions
E. Customer Model Not Listed
Solution:
If old model → Not supported
If new model → Add immediately (Mohsin)
10. Audit Rules
✔ Every pricing change must have internal notes
✔ No manual unofficial pricing allowed
✔ Logs must be retained for 12 months
✔ All changes should be visible in audit trail
✔ Only authorized users may change pricing
11. One-Page Quick Summary (Training Card)
Adding New Model
Brand → Model → Variants → Base Price → Deductions → Test → Publish
Update Pricing
Edit Base Price → Update Deductions → Notify Teams
Teams Involved
Pricing Team → Creates/updates
Tech → Implements
Vendor Ops → Validates & trains vendors
Ops/CX → Communicates
BD Team → Tracks area demand
Management → Approves big changes
Goal:
Accurate, market-aligned, transparent pricing always.