Flutter POS Estimate & Discount Fix

@Microlent

Hello, I understand that your Flutter-based point-of-sale app is almost complete but requires enhancements in two key areas. Firstly, you need the ability to generate estimates directly from the cart screen, ensuring the layout matches existing styles and can be easily shared across Android and iOS platforms. Secondly, there is an issue with the discount calculation logic in the rerun module, causing discrepancies in the final totals. To address these gaps, I propose implementing a feature that allows for the creation of estimates with export options while ensuring accurate discount calculations in the rerun module. By refactoring the discount calculation code and integrating the estimate generation functionality, we can streamline your app's processes and ensure consistent and error-free transactions. With my expertise in Flutter development and experience in handling similar projects, I am confident in delivering the required solutions efficiently. You can view examples of my previous work in my portfolio here: https://www.freelancer.com/u/Microlent I am ready to discuss the project further and provide a detailed plan of action to meet your requirements effectively. Feel free to initiate a chat to discuss how we can proceed with this project. Sincerely, Rajesh

@rajat07me

The missing estimate flow and the discount mismatch are exactly the kind of issues that become painful in a POS app because even a small calculation inconsistency breaks trust in reports. I’d handle this by tracing the cart-to-rerun calculation path first, then adding an estimate generator that mirrors your current receipt structure so the exported document, stored copy, and shared version all stay consistent across Android and iOS. I’ve worked on transaction-heavy logic where totals looked correct in one module but drifted in reprints, summaries, or adjusted records because discount handling was applied in a slightly different sequence. Since your rules are limited to percentage and fixed discounts from Firestore, this is very fixable with a clean normalization pass plus targeted unit tests around edge cases. A short changelog and clean commits are no problem. - Is the current receipt already rendered from a reusable widget/service we can mirror for the estimate output? - Do you prefer PDF as the primary estimate format, or should I choose the most reliable option for both print and share behavior on iOS and Android? - Is the rerun issue happening on both sales and returns, or only on one flow?

@a4logic

Hello, Leveraging on 10 years of professional experience as the founder of A4Logic, my promise to you is straightforward: delivering a high-quality Flutter-based point-of-sale app that perfectly handles your specific requirements is what I excel at. I've built my career and reputation by assisting businesses such as yours in transforming complex ideas into user-friendly and scalable solutions. With expertise ranging from WordPress to Laravel, Python integration to Flutter development, I believe we can seamlessly expand your existing system's capabilities by generating estimates effortlessly and accurately calculating discounts. The mission-critical nature of this project is not lost on me; my job has always been about implementing unyielding solutions for complex problems. My core skills include catering for just such issues as this ill-behaved discount logic. Also, creating code that stands the test of time is crucial, thus I provide clean documenting code quality to actualize free-flowing understanding for both maintenance and thorough code inspection to functionality verifications. Thanks!

@om26er

Hi, I can fix both critical gaps in your Flutter POS app: add a fast Generate Estimate flow with PDF/share/print support on Android and iOS, and correct the discount logic so rerun, sales reports, and receipts always reconcile. I have strong Flutter, Firestore, and POS development experience and will keep the changes clean, tested, and compatible with your existing architecture. I’ll also add unit tests for the discount cases, provide clear commits/change notes, and can walk you through the changes after completion.

@webperfection123

Hi, I can handle both Flutter POS fixes cleanly without affecting your existing sales, returns, or reporting. I’ll add the Generate Estimate action from the cart, create a receipt-style PDF/document, save it locally and to Firestore, and support sharing/printing on Android and iOS. I’ll also fix the discount calculation in the rerun module, verify percentage and fixed discounts against transaction history, and add unit tests to ensure totals, taxes, and net amounts always reconcile. I’ll provide clean commented code, clear Git commits, a short change log, and a brief walkthrough after completion. Please see our portfolio on this link : https://www.freelancer.com/u/webperfection123 Ready to start ASAP.

@gotucat

Hello, I am interested in your Flutter POS project. With extensive experience in Flutter and mobile app development, I am confident I can implement the 'Generate Estimate' feature and correct the discount logic as specified. I will ensure the code is clean, well-commented, and pushed to your Git repository, with a short change log for QA. I understand the importance of accuracy and quick response, and I am available for a brief walk-through of the changes. Looking forward to helping you make this system reliable and efficient. Best regards, SYMLINK TECHNOLOGIES LLP

@joomextensions

Hi, both tasks are clear. First, I will add a Generate Estimate action on the cart screen that creates a PDF with the same layout as your receipt using the pdf and printing packages, saves a copy locally and in Firestore, and can be printed or shared on Android and iOS. Second, I will review the discount logic in your Dart service class for returns; usually the return does not prorate percentage or fixed discounts per line item. I will fix it so return totals reconcile with the day-end report and add unit tests for both discount types. Can you share repo access? Regards, Harsh Thoriya

@adeelpirzada

Hi, I am Adeel. I shipped ComicBase, a .NET MAUI app live on both the App Store and Google Play, so I know the discipline needed to ship a clean fix on both platforms without breaking existing flows. For the estimate feature I would reuse your receipt layout as a template and generate PDF output with a share sheet, storing a copy locally and in Firestore. For the discount bug I would isolate the Dart service class, write unit tests around each discount type first, then patch until totals reconcile with the day-end report. Happy to walk you through the diff on a short call once pushed, and I can start this week. Are the percentage and fixed-amount discount rules ever combined on a single sale, or always mutually exclusive?

@ZohaibRoy

⭐⭐⭐⭐⭐ Create Estimates and Fix Discounts in Your Flutter POS App ❇️ Hi My Friend, I hope you are doing well. I've reviewed your project requirements and see you're looking for enhancements to your Flutter-based POS app. Look no further; Zohaib is here to help you! My team has completed over 50 similar projects for Flutter apps. I will create an estimate feature directly from the cart and fix the discount logic to ensure accurate totals. I will use best practices to deliver clean code and a smooth user experience. ➡️ Why Me? I can easily handle your POS app updates as I have 5 years of experience in Flutter development, focusing on app enhancements, debugging, and creating user-friendly features. I also have a strong grip on Dart programming and Firebase integration, ensuring all aspects of your project are covered. ➡️ Let's have a quick chat to discuss your project in detail and let me show you samples of my previous work. I'm excited to collaborate and ensure your app meets your needs! ➡️ Skills & Experience: ✅ Flutter Development ✅ Dart Programming ✅ Firebase Integration ✅ UI/UX Design ✅ Mobile App Debugging ✅ API Development ✅ Code Refactoring ✅ Document Generation ✅ Unit Testing ✅ Version Control (Git) ✅ Performance Optimization ✅ Problem Solving Waiting for your response! Best Regards, Zohaib

@seefattechnologi

SURE-----------READY to fix it ------------>>Two small gaps are creating a big trust problem: an estimate must match the cart exactly, and a discounted transaction must reconcile everywhere. I can fix both without disturbing your existing POS workflows. I will add the Generate Estimate flow directly from the cart, with receipt-matching layout, PDF/share support for Android and iOS, local + Firestore storage, and then trace the Dart discount calculation to ensure percentage and fixed discounts produce identical totals across rerun, sales reports, and receipts. I will also add focused unit tests, clean up the calculation logic, commit the changes clearly, and provide a concise QA change log. Quick Questions Can you share the current Flutter repository and the discount service class? Is PDF generation already used anywhere in the existing app? I can start by reproducing the discount mismatch, fix the calculation at its source, and verify the complete flow end-to-end.

@jafarali14

Hi Sir Madam I am a Flutter developer with 5 plus years of experience working on POS, billing, reports and business applications. I understand this is a focused but mission critical fix, so I will preserve your existing flow and make only the required changes. I can add Generate Estimate directly to the cart screen with the same receipt style, including items, taxes and discounts. I will make the document available on both Android and iOS for saving, printing and sharing, while storing a copy locally and in Firestore. For the rerun discount issue, I will trace the existing Dart service and Firestore discount rules, identify why percentage and fixed discounts are producing mismatched totals, then refactor the calculation so rerun, sales summary, transaction history and receipts use the same verified logic. I will also add unit tests for both discount types and edge cases, run regression testing and provide clean commented commits with a short QA change log. Skills Flutter Dart Firebase Firestore PDF and document generation POS and billing workflows Unit testing and debugging Git and production deployment Published apps EasyBalance App Store Wynette Logistics App Store MyKidsEdu App Store I can walk you through the changes on a brief call after delivery. Thanking you All the very best Cheers

@Synet

The real key to getting this point of sale fix right is making sure the estimate output matches your existing receipt format completely while the rerun module calculation logic syncs perfectly with Firestore data. I will start by reviewing your Dart service class to map out the exact discount rules and the layout structure you need for the quotation export. Before touching any code, I will share a clear UI design and document layout for your approval so you can see how the estimate button and the share dialog will look on both Android and iOS devices. For the build, I will update your Flutter frontend to add the smooth estimate action directly on the cart screen and refactor the calculation logic in your Dart service class using clean state management so the discount totals always reconcile with your day end reports. After pushing the code to your Git repository, I will run full unit tests and record a short walkthrough video showing the estimate generation and the corrected rerun module in action, along with a detailed change log for your QA team. Milestone payments will be released safely after each stage is completed and fully approved by you, so we move forward step by step with complete transparency. Let us have a quick chat before you award this so we can align on the details. Salma

@ranjika08

Your main issue is consistency under real checkout conditions: once a discount is applied, the rerun numbers stop matching the transaction history, and that creates trust problems in a POS very quickly. I’d isolate the discount calculation flow in the Dart service, correct the reconciliation logic, and then add the estimate action on the cart page so taxes, discounts, and item lines carry over exactly into a shareable document. This is the kind of Flutter maintenance work that benefits from being narrow and test-driven. Because the calculation code is already centralized and the discount types are simple, the fix can stay contained, with new tests proving the same net amount appears in rerun, summary, and receipt output. I can also structure the commits so QA can verify each change without digging through unrelated edits. - Do you want estimate generation to support thermal-style receipt formatting only, or a fuller A4-style layout too? - For Firestore storage, should the saved estimate include just the rendered document reference, or the full cart payload as a reusable quotation record?

@CANWS

Hi, I’m Mayank. I can handle both updates in your existing Flutter POS without changing the working sales/tax logic. * Add Generate Estimate directly from the cart * Generate a receipt-style PDF/document, save locally + Firestore, and support Android/iOS sharing * Fix the percentage and fixed discount logic in the rerun module * Ensure rerun, sales summary, and receipts always reconcile * Add unit tests for the corrected calculations * Provide clean commits and a short change log Since the calculation logic is already isolated in one Dart service, I can keep this focused and avoid unnecessary changes to the existing system. I can start by reviewing the current cart/document generation and discount service, then make the changes and ✅walk you through them on a call. Thanks

@axiomswb

Your Flutter POS discount fix and estimate generator are exactly the kind of mission-critical gaps I specialize in closing. I read your brief closely. The rerun module produces wrong totals whenever a discount fires, while core sales and taxes stay correct — that pattern almost always means the discount is being subtracted at the wrong point in the calculation chain, either before or after tax is applied, rather than a Firestore data issue. I will trace the Dart service class step by step, find where percentage and fixed-amount discounts diverge, and refactor so the net amount matches across the rerun module, sales summary, and printed receipt every time. For the estimate feature, I will use the pdf and printing packages since they produce native PDFs that open a share dialog in well under three seconds on both Android and iOS, with no WebView overhead. The layout will mirror your existing receipt style, and a copy will be stored locally and in Firestore on generation. One risk worth flagging: if your Firestore discount documents store values inconsistently — say, 10 as a percentage in some records and 0.10 in others — the refactor needs to normalize on read, not at calculation time. I will audit that as part of the fix. All changes arrive with commented commits, a change log QA can follow, and new unit tests covering every discount type. Delivery: 3 days, USD 250.

@mrresearcher99

Hello, I’m a mobile and full-stack developer with 10 years of experience building Android and iOS applications, including POS and business management systems. I can extend your existing Flutter application without disrupting the current sales, returns, reporting, or Firestore workflows. I would add the cart-level estimate generation with matching items, taxes, discounts, and receipt-style formatting, supporting local storage and sharing on both platforms. I’ll also trace the existing Dart calculation service to correct the discount logic and ensure rerun totals reconcile consistently with transaction history, summaries, and receipts. I’ll focus on clean, maintainable code, accurate financial calculations, Firestore integration, performance, and targeted unit tests covering percentage and fixed discounts. Let’s discuss the existing calculation service and estimate format. Best regards

@sufyanasmat38

Hi, we have experience with Flutter, Dart, Firebase/Firestore, PDF generation, local storage, and financial calculation workflows. We can add the estimate flow directly from the cart, match the existing receipt layout, save it locally and to Firestore, and support sharing/printing on both Android and iOS. We’ll also trace the discount calculation against transaction history and day-end totals, fix the underlying logic, and add focused unit tests to prevent regression. Clean commits, a QA-ready changelog, and a walkthrough call will be included. We can start immediately. 1. Is the existing receipt generated through a reusable template/service that we can extend for estimates? 2. Can you share the current Dart calculation service and a sample transaction where the discount produces an incorrect total?

@elishadiah326

Hi, Thank you for posting this good task! I work in Flutter with Firestore-backed apps, so both pieces are familiar. For the discount bug: likely an order-of-operations issue, discount applied to the wrong subtotal (pre-tax vs post-tax), a percentage rounding at the wrong step, or the rerun module recalculating from raw cart data instead of the stored transaction totals. Since it's isolated to one Dart service class, I'd trace it against real discounted transactions, percentage, fixed-amount, and tax plus discount together, comparing intermediate numbers against the day-end report to find exactly where they diverge, rather than guessing and patching. For the estimate feature: a "Generate Estimate" action on the cart screen reusing your receipt layout, exported as PDF by default for reliable sharing on Android and iOS, stored locally and synced to Firestore, opening the native share dialog immediately. I'd write unit tests covering the corrected discount logic across all three scenarios, push clean commits with a short change log, and I'm happy to walk you through the fix on a call since this is mission-critical. I can start immediately and work full time. Best regards, Diah

@hassanmustafa01

Hello!⚡ Thank you for the clear brief — adding estimate generation to the cart and fixing the discount logic in your rerun module so every total reconciles is exactly the kind of focused Flutter work I do well. I recently added PDF export to a Flutter POS matching its receipt layout, and fixed a discount-calc bug in a single Dart service so totals matched history. A few things I've built: [your portfolio URLs] How I'd approach yours: 1. Add a "Generate Estimate" action on cart/checkout reproducing items, taxes, and discounts exactly in your receipt style. 2. Save a copy locally and to Firestore, and open the share dialog within three seconds, on both Android and iOS. 3. Trace the discount bug in the rerun module's Dart service — percentage and fixed-amount rules from Firestore. 4. Refactor it so post-discount totals reconcile with the day-end report and transaction history. 5. Confirm the net amount matches across rerun, sales summary, and printed receipt. 6. Add unit tests covering the fixed discount logic, push clean commented commits with a change log, and walk you through it. I'll share relevant Flutter work, and make this a success with you. Thanks. Hassan