ERPNext Supplier ETA Portal

@ukroficer

✅ Hello, We can build this ERPNext Supplier ETA Portal as a custom Frappe/ERPNext module with a Delivery Schedule Workbench, line splitting with strict quantity integrity, and bidirectional Excel import/export that maps child rows back to PO lines. We’d start by defining the Delivery Schedule/Item DocTypes and validation rules, especially around split batches, scrapped replacements, and hiding fully delivered lines without touching inventory or accounting. - Frappe/ERPNext custom app with MariaDB and custom DocTypes for schedule parent/child. - Server APIs for Excel export/import, row mapping, validation, and rollback on errors. - UI in Frappe Desk with split actions, inline edits, filters, and Show All/archive views. - Tests for qty rules, status behavior, import edge cases, and deployment to your ERPNext env. We’re a Preferred Freelancer team from Ukraine with 8+ years, 580+ 5★ reviews, and 740+ completed projects. Is this for an existing ERPNext codebase, and if so which ERPNext/Frappe version is running? Do you want the workbench as a standalone page only, or also embedded into Purchase Order forms? Please let me know your thoughts. Looking forward, Roman

@ahmadayaz

The goal is to enhance visibility and control in delivery management within ERPNext by developing a module with features like unified delivery schedule views, line-level splitting, independent status tracking, data import/export, and filtering/sorting functionalities. The approach involves creating custom Doctypes, adding a table field in Purchase Orders, and developing import/export APIs for Excel integration. Client-side development for an intuitive UI using Frappe's framework and JavaScript logic for real-time validation are key. Workflows include splitting deliveries, handling scrap, and offline capabilities. Out of scope areas are automated inventory management and financial adjustments. The focus is on user experience, performance, and scalability. Let's collaborate to optimize your procurement operations.

@OutsourceMan

Dear Valuable Client, At CnEl India, we specialize in Frappe/ERPNext custom module engineering, complex child-table data architectures, and high-performance server-side APIs. We can develop your ERPNext Supplier ETA Portal & Delivery Schedule Workbench to provide complete, line-level delivery tracking and offline Excel synchronization without impacting your core accounting or inventory stock logic. Our Project Methodology: Custom DocType & Architectural Design: Engineered clean parent/child DocTypes (Delivery Schedule & Delivery Schedule Item) linked to Purchase Orders. Implement server-side hooks ensuring strict quantity-integrity validation across split lines. Spreadsheet-like Workbench UI: Build an intuitive client-side Frappe interface featuring row-splitting tools, non-inventory status tagging (In Production, Delivered, Scrapped, Suspended), live filtering, and auto-archiving of completed POs. Bidirectional Excel Sync Engine: Develop robust Python import/export APIs that seamlessly serialize flattened child-table data into 1:1 Excel sheets, with full validation error reporting during re-imports. Testing, Deployment & Documentation: Conduct rigorous QA across all use cases, deploy custom app packages to your bench environment, and deliver complete source code and technical runbooks. Ready to start immediately! Best regards, CnEl India Team

@gotucat

Hi, I reviewed the ERPNext Supplier ETA Portal request to replace the single-date-per-line model with a Delivery Schedule Workbench for purchase order line batch scheduling. I’ll implement custom doctype and child table records, including Delivery Schedule Item fields like part_no, revision, required_date, promised_date, status, and a_company_pn. I’ll build the spreadsheet-like workbench in ERPNext with JavaScript for real-time split quantity validation, enforce quantity integrity on import, and support bidirectional Excel sync with 1:1 exported rows. I’ll ensure clean, robust validations so statuses remain non-inventory and won’t affect stock or “ordered against invoiced”. Let’s discuss here now.

@seefattechnologi

ERPNext Supplier ETA Portal-----------Positively here to complete your given core expectations and I am sure you will HAPPPY with my work .Just ping me to get highly professional and PERFECT Work or set a quick meeting for the requirement discussion and get started. My Laravel/PHP experience with complex business workflows and ERP integrations would translate well to this custom ERPNext module. If you share your current ERPNext version and Purchase Order customization, I can quickly identify the cleanest implementation approach. Please ping me to get started and get outstanding results. Thanks!!!

@techplusintl

Hi, ★★★ ERPNext Specialist ★★★ I can develop a comprehensive delivery management module tailored to your specifications. To implement this, I will create a new custom DocType for the Delivery Schedule, ensuring it aggregates data effectively. The child DocType will manage individual delivery rows, enforcing strict quantity integrity to prevent discrepancies. I will utilize Frappe's UI framework to ensure a responsive, spreadsheet-like interface for ease of use. For data import/export, I will develop server-side scripts to handle CSV/Excel files, ensuring validation checks are in place to maintain data accuracy. Testing will involve verifying the functionality of batch splitting, status updates, and the integrity of the data during import/export processes. To get started, I will need access to your ERPNext instance and any existing data structures you currently use. Thanks!

@rizwange4

Hi, I can develop this custom ERPNext/Frappe Delivery Schedule Workbench with a spreadsheet-like interface and full batch-level delivery tracking. I’ll implement the custom DocTypes and child tables, line splitting with quantity validation, independent delivery statuses, scrap/replacement tracking, Excel import/export, filtering/sorting, delivered-item hiding, PO completion/archive logic, and the required Frappe UI/API functionality. The module will remain completely separate from inventory, accounting, Purchase Receipts, and invoicing, as required. I’ll also ensure Excel imports are validated before applying any changes and maintain proper traceability for split and replacement batches. I can review your existing ERPNext setup and provide a clean implementation that integrates safely with the current Purchase Order workflow. Best regards, Muhammad Rizwan LA

@starttechno

ERPNext Supplier ETA Portal needs a purpose-built Delivery Schedule Workbench, not a modification that risks inventory or accounting behavior. I would create the Delivery Schedule parent DocType with Delivery Schedule Item child rows, preserving a stable schedule-row identifier so normal lines, split batches, replacements, and historical changes remain traceable. The Frappe interface will flatten batches into spreadsheet-like rows with Part Number, Revision, Description, Order Number, A COMPANY-PN, required/promised dates, quantity, status, comments, and last-updated time. Split actions will create quantity-balanced rows in the browser, while server-side validation will prevent edits or imports whose totals do not match the Purchase Order line. Status changes will remain informational and will never create receipts or update stock. I will implement export/import using Frappe server methods with atomic validation, clear row-level error messages, and support for copied Excel rows representing new splits. Filtering, sorting, Show All behavior, fully delivered hiding, and completed-PO archiving will be included. I will also add the Purchase Order linkage and test edge cases such as scrap/replacement, duplicate rows, invalid dates, and partial deliveries. Muhammad Saad

@Hubready

Hello!, This is James from Hollywood... I read your ERPNext Supplier ETA Portal requirement carefully. The main pain point here is not just showing ETAs, but making supplier updates reliable, traceable, and easy for your team to manage without endless follow-ups. I can build a clean ERPNext module where suppliers update ETAs through a simple portal, while your team gets clear visibility, status tracking, and exception handling. My approach: 1. Map the delivery flow inside ERPNext 2. Build the supplier portal with secure access 3. Connect it to ERPNext records and workflows via API 4. Add validation, audit trail, alerts, and edge-case handling 5. Test with real scenarios so it works in daily operations I pay attention to the small details, so I’ll make sure this fits your workflow instead of forcing a generic setup. Relevant examples from my work: - Vendor shipment tracker for a distribution company - Custom ERP dashboard for a manufacturing client - Supplier self-service portal for purchase order updates - Internal delivery status monitoring system Quick questions: 1. Should suppliers only update ETAs, or also add notes and documents? 2. Do you want this inside ERPNext, or as an external portal syncing by API? 3. What should happen after an ETA change, auto-update, review, or alerts? If you share your current ERPNext flow, I can suggest the best build path right away.

@crtvecode

Your project on developing a delivery management module within ERPNext caught my attention, especially with those focus on enforcing quantity integrity. I see the need for the system to make sure that the total of all delivery rows matches the ordered quantity, which is important for accurate order management. Additionally, the bidirectional Excel sync for 60 orders and 508 lines will simplify data handling, making it easier for your procurement team. And I plan to build a custom Delivery Schedule Workbench that allows users to split delivery lines while maintaining strict quantity checks, the interface will use Frappe's capabilities to provide a user-friendly experience, enabling easy editing and real-time validation. I’ll kind of make sure that the import/export logic handles the child table data correctly, keeping everything organized and functional. I'm ready to get started on this right away for a total of 329 USD, looking forward to collaborating on this project! Rajavel ERPNext Developer | Frappe | Excel Integration

@ozbas

With over a decade of experience as a full-stack software engineer, I am more than equipped to take on your ERPNext Supplier ETA Portal project. I have expertise in various programming languages including PHP, JavaScript, and Ruby on Rails which are essential for developing a comprehensive delivery management module that aligns with your requirements. Furthermore, I am well-versed in API development which lends itself perfectly to the data exchange aspect of this project. One of my key strengths lies in my ability to create powerful yet user-friendly interfaces like the one you need for the delivery schedule workbench. I have excellent skills in front-end development using frameworks such as React and Vue.js, and can create dynamic rows and implement comprehensive filtering and sorting functionalities with ease. My proficiency in working with "child table" data structures ensures that the complex nature of your delivery schedule will be expertly handled. Finally, one aspect that sets me apart is my unwavering commitment to not just completing a project but ensuring its long-term success. Even after successful completion, expect daily communication, free technical support and well-commented source code for seamless future maintenance or update requirements. In choosing me for this project, you're opting for a 360-degree solution with complete dedication from start to finish. Let's discuss further how we can bring your vision to life effectively and efficiently. Thank you!

@corpmember29

Hello, ERPNEXT SUPPLIER ETA PORTAL {{{ I HAVE CREATED SIMILAR BEFORE AND I CAN SHOW YOU }}} I understand you need a custom delivery management module inside ERPNext that replaces the single-date approach with a flexible, schedule-based system for splitting delivery batches, tracking statuses, and managing quantities without affecting inventory or accounting. I can develop the Delivery Schedule and Delivery Schedule Item DocTypes, spreadsheet-like Frappe workbench, line-level splitting, strict quantity validation, independent delivery statuses, scrap/replacement traceability, filtering, sorting, archiving, and automatic hiding of fully delivered items. I can also implement bidirectional Excel import/export with 1:1 screen representation, child-table handling, row validation, update/create logic, and clear error reporting. The module will remain isolated from Goods Receipts, stock, invoicing, and accounting as required. I have 11+ years of experience in software development, ERP systems, custom modules, APIs, JavaScript, Python, databases, and business workflow automation. I WILL PROVIDE 2 YEAR FREE ONGOING SUPPORT AND COMPLETE SOURCE CODE. I am available according to your convenient time zone and can start immediately. I eagerly await your positive response. Thanks, Christina

@denisSolution

Hi, I'm Denis, a full-stack developer with experience building custom ERP modules and handling complex data workflows in systems like ERPNext. Your project needs a dedicated delivery schedule workbench that replaces ERPNext’s rigid single-date model with a flexible, batch-level system. I’ll design a new parent-child Doctype structure to track each delivery batch independently while enforcing quantity integrity and non-inventory statuses. The core challenge is balancing real-time validation with Excel-based offline edits, so the import/export logic will need strict row-level checks to prevent discrepancies. I’ll build the frontend as a responsive, spreadsheet-like interface using Frappe’s framework, with client-side JavaScript for instant splits and updates. The backend will handle CSV/Excel sync via server-side scripts that validate totals before committing changes to the database. Risk comes from the child table complexity during imports, so I’ll add clear error messages for mismatched quantities to avoid partial updates. I can start working right away. Let's connect and discuss the details. Thanks, Denis.

@AneesaIBA

Hello, I have carefully read your project description and understand that you are looking for a skilled professional to develop a custom ERPNext/Frappe Delivery Schedule Workbench that provides line-level delivery batch management, splitting, status tracking, Excel import/export, filtering, and full quantity integrity without affecting inventory or accounting. To approach your project I will build the solution using custom Frappe DocTypes, child tables, server-side Python APIs, and a responsive JavaScript/Frappe interface. I will implement the spreadsheet-style workbench, batch splitting with automatic remainder creation, independent delivery statuses, real-time quantity validation, Excel/CSV bidirectional synchronization, filtering, sorting, delivered-item hiding, and completed-PO archiving. I have strong experience with ERPNext/Frappe customization, Python, JavaScript, custom DocTypes, child tables, reports, REST APIs, data validation, and workflow-driven business logic. I will also ensure imports identify specific validation errors before applying changes and that existing ERPNext functionality remains unaffected. I’d love to discuss your current ERPNext version and Purchase Order structure so I can confirm the implementation approach and provide an accurate milestone plan and timeline. Best Regards, Rabia Shaikh

@technologiesit

As an experienced Full Stack Developer with a solid background in API Development and ERP systems, I am perfectly equipped to take on your ERPNext Supplier ETA Portal project. My skills extend to include JavaScript and PHP, dragging every detail of the scheduled delivery module into life with granular precision. Having created and deployed over 200 successful projects, including several relating to supply chain management, inventory control, and logistics tracking, my understanding of such requirements is well-rounded. My experience matches up neatly with your project's specific needs for a delivery schedule module: non-inventory statuses; line-level splitting; data import/export compatibility with Excel; filtering/sorting; hidden archiving. Importantly, my solution will not interfere with or disrupt your core inventory/ accounting modules - ensuring the seamless integration of this new functionality into ERPNext. I am confident that I will deliver your project on time and budget. To succeed at complex deliveries like yours, clear communication with the stakeholders is crucial. You will find me a responsive partner through the entire development process and even afterward, for long-term support. Let's turn this idea into a powerful reality that not only transforms your procurement operations but also reflects my commitment to driving result-driven transformations for businesses like yours.

@megauravpanwar

Flattening 508 lines into a high-concurrency Delivery Schedule Workbench requires preventing data race conditions during bulk Excel imports and child-table heavy transactions in Frappe. To enforce strict quantity integrity without locking core inventory or accounting tables, I will build an isolated custom DocType architecture utilizing server-side Python transactional wrappers and a robust Pandas/OpenPyXL pipeline for 1:1 bidirectional Excel sync. Real-time frontend validation will be handled via native Frappe JS UI controllers. Having architected enterprise modules handling high-frequency data states across 15+ years, I ensure zero database bloat and strict transactional rollbacks on integrity failures. Let us discuss schema locking and milestone kickoff. Gaurav Panwar Senior Full-Stack & System Architect (15+ Yrs Exp)

@Hrolgar

Frappe doesn't let a child table doctype contain another child table, so the batch-level delivery rows for a PO Item can't nest inside Purchase Order Item itself. They'd need a separate doctype linked back to the parent PO Item's parent/parentfield/idx, which is also what makes quantity-integrity possible: sum the batch rows and validate against item qty on every split, scrap, or replace, not just on save. The Excel side breaks in a specific way if rushed. Frappe's Data Import Tool matches child rows by row name on update, and if an export doesn't carry that name back in, a re-import deletes and recreates rows instead of updating them, duplicating or orphaning delivery history. I'd build export/import keyed on row name, not position, so re-imports stay idempotent. Non-inventory states (In Production/Delivered/Scrapped/Suspended) sit as a status field on the batch row, transitions validated server-side, and the fully-delivered filter is a saved report plus an archive job clearing closed lines out. 750 over 7 days is what the brief as posted supports. What could move it is whether open PO lines need backfilling into the new structure, or this only applies going forward. M1: doctypes, schema, quantity-integrity validation. $250, 2 days. M2: batch status tracking, split/scrap/replace logic. $250, 3 days. M3: bidirectional Excel import/export, filtering/archiving. $250, 2 days. I'd start on M1, that locks schema and validation before the Excel sync.

@kishanbwts

This delivery schedule workbench concept fits a complex procurement process well, and your main challenge is combining granular batch-level tracking with intuitive use inside ERPNext. I’ve tackled similar projects where standard purchase order line structure in ERPNext limited flexibility, so I built custom child table solutions that allowed line splitting, independent status fields, and strict quantity validation. For example, one client’s procurement team needed exactly this level of batch control with Excel import/export syncing and quick filtering, and the UI had to feel like a spreadsheet for better adoption. To ensure smooth import/export, I typically map parent-child relationships explicitly and handle row validation server-side to stop partial data errors early. I’d start by creating the Delivery Schedule and Delivery Schedule Item doctypes, then layer on front-end splitting logic with real-time totals update and status tracking. For usability, adding “Show All” toggles and automatic archiving would be key. A couple of questions before starting: - Should the Excel import reject entirely on any data issue, or allow partial updates and report problematic rows for correction? - How many concurrent users do you expect to update scheduling at once? That affects conflict resolution design. I’m ready to develop the module incrementally with tight testing on the import/export and quantity integrity rules so you get a reliable, user-friendly delivery schedule workbench fast.

@hirewordpress

Hi, I have carefully reviewed your requirements for the ERPNext Delivery Schedule Management Module, and I would be happy to help develop this solution. I understand that the goal is to create a flexible delivery planning and tracking system within ERPNext without affecting the existing inventory, accounting, Purchase Receipt, or invoicing processes. The key requirement is to move beyond ERPNext's standard one-delivery-date-per-Purchase-Order-line approach and allow a single order line to be divided into multiple independently managed delivery batches. My Understanding For example, if a Purchase Order contains 100 units of a part, it will initially appear as one delivery schedule row. If the delivery needs to be split, such as 5 units being delivered separately, the system should create two independent rows: 5 units with its own date and status 95 units with its own date and status The system will maintain strict quantity validation to ensure that all schedule records remain properly linked to the original Purchase Order quantity. The delivery statuses—In Production, Delivered, Scrapped, and Suspended—will be informational only and will not automatically update stock, create Purchase Receipts, or affect accounting values. Proposed Development Approach Delivery Schedule Workbench I would develop a centralized, spreadsheet-like workbench displaying one row for every scheduled delivery batch. Allow the system to validate and update the schedule. Regards, Raman