Analyzing the archives I came across my three-year-old script to manage the windows of online store deliveries. The script is called The Maasdam Project in honor of the holes from the cheese.Why is this?
Any online store has to solve the problem of scheduling deliveries and communication with the buyer:
- on which day you can deliver?
- in what time interval (window) can it be made?
- Is it possible to shove another order in this window or will the delivery service burst?
')
To solve this problem, a prototype was written, which allowed us to mark geographic delivery zones, create a service schedule and give the buyer a clear interface for independent selection of a convenient interval.
Where to get?
The project can be taken
here . I do not spread the server part, as I was strongly tied to a closed framework. From the client side, I cleaned everything that had nothing to do with this framework :)
Package Description
/api.txt - description of the server API for managing the schedule and getting delivery zones
Please note that there is no user role management there: the script was in the prototype stage and we didn’t screw such restrictions.
/structure.txt - description of the database structure for data storage
Back Office Script
/www/contract.html - Back office script for managing delivery zones and service schedule. Tab descriptions:
Zone Marking

On this tab, you can add, delete, edit and mark delivery zones, call them and assign shipping costs by area.
Schedule template

This tab defines the basic weekly schedule template for each delivery zone. Here you can also set the maximum capacity (number of deliveries) for the morning, afternoon and evening time windows
Schedule editor

Manage the delivery service calendar (the calendar is created based on a weekly template).
The script of the client part of the store

/www/maasdam.html
By clicking on the map or when determining the address from the search, a bubble is displayed in which the customer can select the nearest convenient delivery window.