Evergreen farms (pos)

Private

Project *AFC APPFORSOLARArrow LogisticsArtificial Intillegence  » Algo Trade Automation  » Algo Trade Manual  » Bulk mail Automation with web interface  » Bulk Mail Service For Bench Sales  » Code Generation Tool  » Cold Emailing Automation (AI-Driven)  » Invoice Inventory Automation  » invoice to inventory for evergreen  » Test Automation  » What's app Bulk messaging with AI agents  » Zelle Payment for evergreenAsk RideCharan Technologies _ DevelopmentEver green Farms USA (static website)Evergreen farms (pos)Evergreen React ApplicationFinwareGas Station ERPHackthonIT HappENSLucky BraidsMy Produce StandNexPumpNexZen Printer AgentNoxa_JewelleryOffice Requirments  » Daily Tasks For Madhu  » Employees requirements  » Recruitment senior mern stack developer  » Red MIne Speed  » Senior Mern Stack DeveloperOPT - (USA) UpdatesQA TestersRare FruitsRegal SolarRegal Solar DMRegal Solar Energy_ ReactReliance Home Builders_ reactRemit2AnyRestaurant POSRSVPRushi GardensRV_ EngraverSoloar AppSri Farms _ DMSri_FarmsSuthra QNova LabsTech FourceTechnical RequirementsTechy_DevelopmentTechy_POS Travel Mate

Tracker *Bug Feature Support Testing

Subject *

Description Edit # Lawn Mowing Subscription – Job Scheduling Requirements 1. For Lawn Mowing subscriptions, customers should have two options: * Select the visit months manually. * Allow the system to automatically generate the visit months based on the plan (e.g., 6 visits/year = 6 evenly distributed months). 2. After OTP verification, show the selected/system-generated visit months in the Order Summary. 3. Customers can change the visit months only. They cannot change the total number of visits defined by the subscription plan. 4. For each selected month, create one job automatically. 5. The preferred job creation date is the **1 / 15th** of the selected month. 6. Before creating the job, check the number of Lawn Mowing jobs already scheduled for that date. * If fewer than **15 jobs** exist, schedule the job on the 15th / 1st. * If **15 jobs** already exist, move to the next available day (16th, 17th, etc.) until a day with available capacity is found. 7. If a customer subscribes **after the 15th**, do not create a job on a past date. Start checking from the current date and schedule on the next available day with fewer than 15 jobs. 8. Before creating a job, verify that a job for the same subscription and visit month does not already exist. 9. After jobs are created, arrange the daily schedule based on customer addresses and travel distance for efficient routing. 10. All scheduling must use the **company timezone**. 11. Do not change or break any existing Subscription, Job Management, OTP Verification, or Checkout functionality.