CODEREYES IMEI LEDGER FOR MOBILE SHOPS
Codereyes IMEI Ledger for Mobile Shops compatibility with REEID Translate
Codereyes IMEI Ledger for Mobile Shops compatibility with REEID Translate is being reviewed using official plugin documentation. Tracks second-hand mobile phone inventory by IMEI, recording purchase and sale history including seller/buyer details, NID, and pricing. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Codereyes IMEI Ledger for Mobile Shops does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Codereyes IMEI Ledger for Mobile Shops is documented in the Other category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Codereyes IMEI Ledger for Mobile Shops compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Tracks second-hand mobile phone inventory by IMEI, recording purchase and sale history including seller/buyer details, NID, and pricing.
- Provides real-time profit/loss calculation during sales entry and generates reports for stock, sales, and profit over customizable date ranges.
- Includes duplicate protection that prevents adding phones already in stock and warns if a previously sold phone is being bought back.
- Supports search functionality using full or partial IMEI, names, mobile numbers, NIDs, and models, with compatibility for Bengali digits.
- Offers CSV export capabilities formatted for Excel, preserving Bengali text, treating IMEIs as text to prevent scientific notation, and neutralizing formula injection risks.
- Integrates with BTRC NEIR via direct links for IMEI verification and supports custom currency symbol configuration through filters.
TRANSLATION BOUNDARY
Codereyes IMEI Ledger for Mobile Shops capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
Codereyes IMEI Ledger for Mobile Shops and REEID Translate FAQ.
What does Codereyes IMEI Ledger for Mobile Shops do?
Codereyes IMEI Ledger for Mobile Shops has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Codereyes IMEI Ledger for Mobile Shops have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Codereyes IMEI Ledger for Mobile Shops?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Codereyes IMEI Ledger for Mobile Shops in a multilingual WordPress workflow.
REEID documents Codereyes IMEI Ledger for Mobile Shops functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.