Bagisto Marketplace Delivery Time Slot SaaS

Tenants build the default windows every seller falls back to. Each window holds a date, a time range, a booking quota, and a processing period.

Several windows go onto one date from the same screen. The module refuses a second window at the same date and start time.

• Create default windows for any date, several at a time.
• Set a time range, a quota, and the minimum processing days.
• Edit the date, time range, or quota of a saved window.
• Activate or deactivate a window to control what checkout offers.
• Delete one window, or select several and delete them together.
• Quotas outside the range of 1 to 99999 are refused on save.

One Delivery Time Slots list carries every active window in the store. Each row says whether a window belongs to a seller or to the tenant.

Tenants search by seller name or delivery day, narrow the rest by column, then open a seller profile from the row.

• See every active window in one list, marked seller or tenant, with the seller profile a click away.
• Search by seller name or delivery day, and sort by any column.
• Filter by allowed orders, delivery day, start time, and end time.
• Change how many windows appear on each page.

Sellers publish delivery windows from the seller panel, against the products they own. Individual sellers set their times and quotas.

No seller reads or edits another seller's windows. Publishing nothing stays valid, because the tenant defaults cover that seller instead.

• Publish delivery windows against the products they own.
• Set a time range, a quota, and their own processing days.
• Activate or deactivate those windows, and add more to a date.
• A seller never sees or edits another seller's windows.
• Tenant defaults apply to any seller that publishes none.

Configuration holds the rules the seller screens and the checkout both obey.

Tenants switch the module on, pick the delivery weekdays, and set how many dates checkout displays.

Every setting takes a value per channel, and the no-slot message takes one per channel and per language.

• Enable or disable the module for one store.
• Select the weekdays that qualify, and the dates checkout displays.
• Write the message shown when no window is available.
• Show the windows on the product page, and choose whether past ones stay visible.
• Disabling the module blocks its admin and seller screens.

Customers read the delivery windows open to a product before it enters the cart.

Windows arrive grouped by day and date, the same way checkout presents them, while the tenant keeps that setting switched on.

• See the windows available for a product, grouped by day and date, before the cart.
• The block follows the tenant configuration setting.
• Windows come from the seller that owns the product, or the tenant defaults.

Checkout groups the windows per seller. Three sellers in one cart produce three calendars, and products the tenant sells sit under Admin.

Customers pick a checkout delivery slot while placing the order. Full windows disappear rather than grey out, and a shipping method is still required.

• Choose a delivery date and a time window per seller.
• Read one calendar per seller, with tenant products under Admin.
• See only the configured weekdays and number of dates.
• Read a clear message for a seller with no window available.
• Windows at their quota, and dates inside the processing time, stay hidden.
• The chosen windows stay on the cart and reach the order.

Every booking lands in a dedicated Delivery Orders list. Each row carries the seller, the delivery date, the order, and the time window.

Tenants search the list, open an order from it, and export the result. Booked slots also reach the order view and the invoice.

• Search the list, open an order from it, filter by date, order, or seller, then export.
• Delete one booking, or select several and delete them together.
• Read the booked slot on the order, the invoice, and order history.
• Order placed mail reaches the customer, the seller, and the tenant.

Sellers read the bookings taken against orders of their own, in a Delivery Order History list.

Each row carries the delivery date, the order, the chosen window, and the purchase date. Filtering, export, and clearing stay inside that seller.

• See the delivery date, order, chosen window, and purchase date.
• Filter by delivery and purchase date, then export the list.
• Delete one booking, or select several and delete them together.
• Read the booked date and window on their own order view.