I already have a fully-functional Android companion for my web-based POS. All core features and REST APIs are live, and the app can pair with Bluetooth and thermal printers. The only snag is that the bills coming out show incorrect data rather than the precise line-items and totals stored in the POS. Here’s what I need: • Audit the existing API calls in the Android code and confirm the correct endpoints, parameters, and authentication keys are being used. • Adjust any mappings so the app pulls the right invoice payload and sends it unaltered to the print routine. • Tweak the print logic (ESC/POS commands, formatting, or parsing) so what appears onscreen is exactly what appears on paper—no dropped items, wrong totals, or extra characters. You’ll have direct access to: • Source code for the Android project (Java/Kotlin) • API keys and documentation for the web POS • Sample invoices for quick replication of the bug Both Bluetooth and wired thermal printers should output identical, correctly formatted receipts once you’re done. I’m looking to wrap this up ASAP, so if you’re comfortable tracing API flows, debugging Android print tasks, and fine-tuning ESC/POS output, jump in and let me know how soon you can start and deliver the fix.