Re: Accurest Daily Standup Meeting

22 September

failed

Yashaswini Bhoyate <yashaswini.bhoyate@redberyltech.com> 00:00 · Hi Team, Please find below the discussion summary and action items from today’s stand-up meeting for your reference 1. Vendor Shipment and Discrepancy Handling Discussion * The team discussed improvements required for vendor shipment entry and discrepancy management. * A shipment can contain multiple vendors, and the structure should support vendor-wise line items instead of repeating vendor information for every field. * Proposed fields include: * Expected Quantity * Received Quantity * Damaged Quantity * Discrepancy Quantity (auto-calculated as Expected Quantity – Received Quantity – Damaged Quantity) * If the discrepancy quantity is zero, no resolution action will be required. * If there is a discrepancy, the user should select appropriate resolution options through a dropdown. * The team discussed adding better handling for damaged, short, or excess quantities. ________________________________ 2. Cash Flow Date and Payment Due Date Enhancements * The team discussed changes related to payment tracking and cash flow projection. * Required fields: * Cash Flow Date * Payment Due Date * Amount Payable * The system should calculate the remaining payable amount based on completed transactions. * Example discussed: * If total payable amount is 21,570 and a payment of 10,000 is completed, only the remaining balance should appear in future cash flow projections. * The cash flow projection should not include amounts that are already paid. * Users should have the ability to override the default cash flow date when required. ________________________________ 3. Customs Duty Master and Due Date Configuration * The team discussed creating a Customs Duty Master configuration. * The master should support due date calculation based on: * Same month * Next month * Specific number of days * Month-end calculation * The system should allow admins to configure default due date rules. * Based on the selected master value, the system should automatically calculate customs duty due dates. * Cash flow date will default to the due date but can be overridden by users if required. * The configured master values will apply across shipments. ________________________________ 4. Quotation Comparison and Shipment Date Handling * The team discussed improvements required in quotation comparison functionality. * Shipment-related dates such as: * ETA * ETB * ETD * Committed Departure Date were discussed as important fields. * The team discussed reusing quotations for similar future shipments. * Users should be able to update committed departure dates while maintaining quotation details. * Default departure date calculation can be based on CRD (Cargo Ready Date), but users should have the ability to override it based on operational requirements. * The team clarified that quotations are managed through forwarders and should not be directly linked with shipments. ________________________________ 5. Unit Economics and Accounting Integration Discussion * The team discussed unit economics documentation and accounting integration. * Accounting-related discussions included: * QuickBooks integration * Xero integration * Accounting entries * Unit economics calculations * Existing Figma fields and documentation will be reviewed and aligned. * The team discussed completing development activities and coordinating timelines with the respective teams. ________________________________ 6. Development Timeline and Planning Discussion * The team discussed the target completion timeline for development activities. * The expected completion target discussed was end of October. * Due to planned holidays and availability constraints, possible delays were highlighted. * The team agreed to review the overall plan once Santosh returns and align on pending activities. ________________________________ 7. Stock Forecasting and Inactive Product Handling * The team discussed handling inactive users/products in stock forecasting. * If a product becomes inactive: * Existing product hierarchy should continue to work properly. * Forecasting and inventory tracking should handle inactive items appropriately. * The team discussed scenarios where inactive products may still have remaining inventory. * Further clarification is required on how inactive stock should behave in forecasting calculations. ________________________________ 8. Forecasting L4 Updates and Testing Status * The team discussed progress on L4 forecasting-related updates. * Current status: * Some updates are completed. * Testing is in progress. * Versioning-related inputs have been incorporated. * The team discussed completing testing and moving changes forward for release. * Kit-to-component scenarios have been provided for UAT testing. * Remaining work includes L4 screen validation and multiple scenario testing. ________________________________ 9. Channel-Based Substitution Policy and Kit Substitution Discussion * The team reviewed channel-based substitution policy functionality. * Current implementation includes: * Channel priority configuration * Channel-based substitution rules * Kit-to-kit substitution * Kit-to-component fallback scenarios * Testing is being performed for Amazon channel policies. * The team discussed scenarios where: * Kit-to-kit substitution is unavailable. * The system should move to component-level substitution. * OpenProject defects are being reviewed and resolved during testing. ________________________________ 10. Virtual Bundling and Kitting Rules Discussion * The team discussed virtual bundling and kitting configuration. * Key discussion points: * Different clients may have different rules for: * Kit-to-kit substitution * Virtual bundling * Kit-to-component substitution * Some clients may allow virtual bundling while others may not. * The team discussed whether virtual bundling should: * Be enabled by default, or * Require explicit configuration through rules. * Percentage-based fulfillment scenarios were discussed: * Whether clients can configure partial fulfillment percentages. * Whether the algorithm should determine availability. * The team agreed that the configuration approach needs further clarification and confirmation. ________________________________ 11. Follow-up and Next Steps * Prathamesh will share further details/documentation related to: * Kitting * Virtual bundling * Component rules * The team will review the latest Excel/document updates shared. * Development team will incorporate confirmed changes into technical implementation. * Testing and UAT activities will continue for substitution policies and L4 forecasting features. ________________________________ Action Items – Sr. No Action Item Description Owner Status 1 Update Vendor Shipment Discrepancy Handling Implement vendor-wise shipment discrepancy handling with expected quantity, received quantity, damaged quantity, and auto-calculated discrepancy quantity. Development Team In Progress 2 Configure Discrepancy Resolution Options Add dropdown-based resolution options for shipment discrepancies based on shortage, excess, and damaged quantities. Development Team Pending 3 Implement Cash Flow Date Calculation Logic Update cash flow calculation logic to exclude already paid amounts and display only remaining payable amounts. Backend Team In Progress 4 Add Payment Due Date Configuration Implement configurable payment due date rules including same month, next month, number of days, and month-end calculations. Development Team Pending 5 Develop Customs Duty Master Create Customs Duty Master configuration to manage default due date calculation rules. Backend Team Pending 6 Review Cash Flow Date Override Functionality Validate and implement user override capability for cash flow dates where operational changes are required. Product & Development Team Pending 7 Review Quotation Comparison Enhancements Validate quotation comparison flow and confirm handling of ETA, ETB, ETD, and committed departure dates. Product Team Pending 8 Validate Quotation Reuse Scenario Review requirement for reusing quotations for future shipments without directly linking quotations to shipments. Product Team Pending 9 Review Accounting Integration Requirements Review QuickBooks/Xero integration requirements and align accounting entries with unit economics calculations. Integration Team In Progress 10 Complete Unit Economics Documentation Review Review existing Figma screens and documentation to align unit economics requirements. Product Team Pending 11 Complete L4 Forecasting Testing Perform validation testing for L4 forecasting updates and confirm versioning-related changes. QA Team In Progress 12 Validate Kit-to-Component Substitution Scenarios Execute UAT scenarios for kit-to-component fallback substitution logic. QA Team In Progress 13 Resolve OpenProject Defects Review and address reported defects related to substitution policies and forecasting functionality. Development Team In Progress 14 Review Inactive Product Forecasting Behavior Clarify expected behavior for inactive products with remaining inventory in forecasting calculations. Product Team Pending 15 Share Kitting and Virtual Bundling Details Provide detailed documentation and rules related to kitting, virtual bundling, and component substitution scenarios. Prathamesh Pending 16 Confirm Virtual Bundling Configuration Approach Decide whether virtual bundling should be enabled by default or controlled through configuration rules. Product Team Pending 17 Review Percentage-Based Fulfillment Logic Clarify requirements for percentage-based fulfillment and whether configuration should be client-specific. Product Team Pending 18 Align Development Timeline Review pending activities and finalize timelines after Santosh’s availability. Project Team Pending ________________________________ Decision Log – Sr. No Decision Details Owner 1 Vendor-wise Shipment Discrepancy Tracking Shipment discrepancies will be managed at vendor level instead of repeating vendor information across shipment records. Product Team 2 Automatic Discrepancy Calculation Discrepancy quantity will be automatically calculated using expected, received, and damaged quantities. Development Team 3 No Action Required for Zero Discrepancy If discrepancy quantity is zero, the system will not require resolution action. Product Team 4 Cash Flow Should Reflect Remaining Payables Paid amounts should be excluded from future cash flow projections, and only outstanding balances should appear. Product Team 5 Configurable Customs Duty Due Dates Customs duty due dates will be controlled through a master configuration. Product Team 6 User Override for Cash Flow Dates Users should have the ability to modify default cash flow dates when operational requirements change. Product Team 7 Quotations Managed Independently Quotations will remain managed through forwarders and will not have direct shipment linkage. Product Team 8 Departure Date Can Be Updated System-generated departure dates can be overridden based on operational requirements. Product Team 9 Testing Required Before Release Forecasting and substitution policy changes must complete validation and UAT before release. QA & Development Team 10 Channel-Level Substitution Support Substitution policies will support channel-specific rules and priorities. Product Team 11 Kit-to-Component Fallback Support If kit-to-kit substitution is unavailable, the system should support component-level substitution based on configured rules. Product Team 12 Client-Specific Kitting Rules Different clients may require different configurations for kitting, virtual bundling, and substitution behavior. Product Team 13 Further Clarification Required for Virtual Bundling The final approach for enabling and configuring virtual bundling requires additional discussion. Product Team 14 End-of-October Target Discussed Development completion target was discussed as end of October, considering availability and holiday constraints. Project Team Overall Summary: The meeting focused on Accurest enhancements across shipment management, cash flow calculation, customs duty configuration, quotation handling, forecasting improvements, substitution policies, and kitting/virtual bundling rules. Multiple functional clarifications were discussed, with several items requiring confirmation before final development implementation. Regards, Yashaswini ________________________________ From: Yashaswini Bhoyate Sent: Monday, July 13, 2026 4:21 PM To: Santosh Narate <santosh@redberyltech.com>; Prathamesh Badve <prathamesh@accurest.co>; Gaurav More <gaurav.more@redberyltech.com>; Snehal Hendre <snehal.hendre@redberyltech.com>; Saumya Patra <saumya.patra@redberyltech.com>; himal.goyal <himal.goyal@accurest.co>; Mamta Badade <mamta@accurest.co>; Saurabh Tenpe <saurabh.tenpe@redberyltech.com> Subject: Accurest Daily Standup Meeting When: Tuesday, September 22, 2026 11:30 AM-12:00 PM. Where: Microsoft Teams Meeting ________________________________________________________________________________ Microsoft Teams meeting Join: https://teams.microsoft.com/meet/49317656437733?p=xbQ9awYIVwtqyCMhTT Meeting ID: 493 176 564 377 33 Passcode: sr3iq79X ________________________________ Need help?<https://aka.ms/JoinTeamsMeeting?omkt=en-US> | System reference<https://teams.microsoft.com/l/meetup-join/19%3ameeting_YjlkYTdjMjktZTdjYi00MzliLWIyNGItMGU3NDVjODE1NWRm%40thread.v2/0?context=%7b%22Tid%22%3a%2214158288-a340-4380-88ed-a8989a932425%22%2c%22Oid%22%3a%22f127dbd2-f771-468e-9a6f-fed8a834cc3d%22%7d> For organizers: Meeting options<https://teams.microsoft.com/meetingOptions/?organizerId=f127dbd2-f771-468e-9a6f-fed8a834cc3d&tenantId=14158288-a340-4380-88ed-a8989a932425&threadId=19_meeting_YjlkYTdjMjktZTdjYi00MzliLWIyNGItMGU3NDVjODE1NWRm@thread.v2&messageId=0&language=en-US> ________________________________________________________________________________

Summary

Not summarised yet.

Threads

Tags

Speakers