Important
Magic Invoice App is intended for authorized proof-of-purchase recovery, warranty, return, inventory, and support workflows. It helps users rebuild old documents from information they already possess in accounts, PDFs, email receipts, photographs, backups, or the connected iOS device. It does not validate ownership by itself, does not supply private customer records, and must not be used to misrepresent a transaction or create deceptive documents.
| 80 mm Thermal POS |
A4 Office documents |
US Letter Invoices & digital receipts |
Live Print Inspector |
Magic Invoice App goes beyond the thermal roll. The POS engine shares one guided workflow with A4, US Letter, multi-page, and digital receipt formats. Every supported document can be completed section by section, rendered before printing, and checked against the connected device where an IMEI, MEID, or serial number is required.
Choose a thermal POS receipt, an A4 invoice, a US Letter document, or a multi-page digital receipt from the same searchable template browser. The active paper type is always visible before the form opens. All bundled definitions use a normalized form and output contract.
Large forms are divided into clear sections. The document remains visible while the user moves through the form, reducing missed fields.
- Universal Demo Mode: A single privacy control masks sensitive information across the main UI, activity log, history, account surfaces, catalogs, and previews. Masks use asterisks, preserve the visual shape of the interface, and never replace the real value stored for authorized output.
The embedded inspector renders the actual print scene, not a simplified text approximation. It supports thermal output, A4 and Letter pages, zoom, drag, pagination, refresh, and a full review window before printing.
- Draft previews receive explicit placeholders without silently committing sample data to the final document.
- Live preview work is serialized and coalesced to avoid stale or competing renders.
- PDF pages render at high resolution with smooth scaling.
Smart Fill detects the connected Apple device and helps populate supported model, capacity, color, price, part number, description, and item-row fields. The catalog searches the official Apple source first and uses AppleDB only after a genuine miss.
Import an existing PDF or compatible email receipt and let the active definition map recognized values into its own fields. Imported data is normalized before use and cannot replace protected hardware identifiers.
When a format requires an IMEI, IMEI2, MEID, or serial number, Magic Invoice App reads the value from the connected device, fills it automatically, locks the destination field, and verifies it again before output. Product 1 identity remains bound to the connected device.
The application utilizes an advanced, privacy-aware annual licensing model that operates independently from the connected Apple device.
- Account sign-in, annual entitlement, and workstation-seat verification are completely independent.
- A plan can be verified before a device is connected; generation and device-bound actions remain locked until a real supported device is present.
- Windows PCs and Macs use the same seat model and plan limits.
- The workstation identity is a namespaced SHA-256 value. Raw platform identifiers and the connected Apple-device serial are not sent as the workstation ID.
| Plan | Workstations | Annual price |
|---|---|---|
| Personal | 1 | USD 49 |
| Professional | 2 | USD 89 |
| Workshop | 3 | USD 129 |
| Business | 5 | USD 199 |
- Hardware Optimization: Graphical 80 mm receipts are rasterized for ESC/POS transport instead of sending PDF bytes directly to the printer.
- Transports: Raw USB/libusbK, operating-system queues, and configured network transports are handled through the shared print layer.
- Precision: Specific logic implemented for unique receipts (e.g., Cricket receipts use one continuous roll page, exact section spacing, uniform separators, and one final cut with dynamically rendered Code 128 barcodes).
- Fallbacks: Virtual PDF printers remain available for A4/Letter verification when a physical printer is not present.
The catalog presents official device artwork, model identifiers, launch year, storage tiers, launch pricing, and available colors. Resolution follows this strict order:
- Bundled or official Apple source.
- Verified local cache.
- AppleDB fallback only when the primary image is unavailable.
Browse models, storage and finishes |
Reference conversion with cached FX data |
Note
Catalog metadata is assistance for the form, not proof of ownership or a substitute for information read from the connected device.
The internal catalog currently contains over 42 definitions across Apple, AT&T, Bell, Best Buy, Boost Mobile, Claro, Cricket Wireless, JB Hi-Fi, T-Mobile, The Source, Verizon, and Videotron families. Depending on the source format, a definition produces:
- Continuous 80 mm POS output;
- A4 or US Letter documents;
- Multi-page contracts and agreements; or
- A custom physical page size declared by the definition.
Each definition owns its fields, calculations, preview mode, physical page specification, and renderer. The main application does not guess retailer data or silently generate transaction values.
Magic Invoice App is built from the ground up to offer the same source-level feature set to Windows and macOS natively.
- Windows and macOS build scripts pin Python 3.11.9 and pymobiledevice3==6.1.5.
- Windows definitions compile to native
.pydmodules; macOS definitions compile to native.somodules from an isolated staging tree. - Platform-specific printer discovery is separated from the document engine.
- A manifest records SHA-256 hashes for every packaged definition and prevents modified or unknown plugins from loading in frozen releases.
Liquid Glass UI Light and dark themes across the main workspace and dialogs. |
English / Spanish Native A central translation registry prepared for additional languages. |
The application exposes a strict internal definition contract. Developers can create and validate a definition in a source checkout today. This is an authoring API, not yet a public installable SDK.
See docs/DEFINITION_AUTHORING_GUIDE.md for:
- Folder and module structure.
- Field, item-table, preview, and output schemas.
- Device-identity and privacy rules.
- Sample data and renderer hooks.
- Automated contract and document tests.
- Use only references and assets you are authorized to process.
- Do not include customer PII in source examples, screenshots, fixtures, or bug reports.
- Do not disable definition-manifest verification in distributable builds.
- Never bind an annual workstation seat to a connected customer's device identifier.
- Report security-sensitive issues privately before publishing technical details.
Warning
Bugs can happen. Operating-system updates, printer drivers, USB controllers, device pairing, third-party libraries, and differences between receipt files can produce behavior that cannot always be predicted or reproduced by the project.
If something does not work correctly, please report it through GitHub Issues. Please include:
- The application version and operating system.
- The selected definition and paper type.
- A screenshot or short GIF showing the problem.
- Relevant Activity Log lines.












