Configure date-based availability, rental duration, rate plans, deposits, buffers, item or quantity reservations, extensions, delivery or collection, returns, care, damage review and repeat availability across a client-owned rental business.
The Rental Commerce module is the rental logic and operational engine. It can power a client-owned website, B2B portal or supported connected channel without requiring the client to list inventory on CostumePeti or use Vault-managed storage.
The same rental engine can support different user journeys while retaining one availability, reservation and return model underneath.
Allow eligible users to choose dates, inventory and delivery options directly through an approved client-owned storefront.
Support shortlist, consultation, availability review, quotation or approval before the rental becomes committed.
Run project, event, production, stylist or corporate rentals with larger quantities, kits, multiple dates and responsible users.
Rental pricing and booking should not sit separately from warehouse availability, fulfilment or return status. The complete lifecycle determines whether inventory can be promised again.
Configure duration, rate plans, deposits, minimums, blackout periods, promotions, extensions and commercial conditions.
Protect items, variants, quantities, kits and full date windows using holds, reservations, buffers and conflict checks.
Connect preparation, picking, dispatch, collection, delivery, handover, active-use state and approved extensions.
Verify return, components and condition, route care or damage and calculate the next trustworthy available date.
Start with the complete Rental Commerce architecture, then move through rate rules, deposits, buffers, calendar availability, holds, reservations, fulfilment, active-rental status, extensions, returns, condition, care, adjustments and next availability.
Rental rules can be configured at the client, category, collection, item or approved account level depending on the implementation model.
Commercial rules should remain separate from the physical inventory identity so the same asset can retain one custody record even when rental values or policies change over time.
Configure how rental value changes with the approved rental period.
Apply the relevant security and commercial requirements.
Protect operational time around the visible rental period.
Control dates that cannot be rented and extensions that affect the next commitment.
Rental availability should consider the selected use period plus preparation, transit, return and care time, as well as existing commitments, maintenance blocks and physical stock state.
Unique items, variants, quantity stock and kits can use different reservation logic while still feeding one client-facing availability experience.
Calculate the complete blocked period around the proposed rental.
Commit the correct physical stock model to the selected dates.
Support assisted selection or checkout without leaving inventory locked indefinitely.
Stop overlapping commitments and surface practical replacements.
Once a rental is confirmed, Commerce OS can route the required operational work to the client team, Vault-managed operation or supported connected provider according to the implementation model.
The active-rental state should identify what is out, with whom, where applicable, until when and under which project or account context.
Translate the confirmed reservation into an executable warehouse or store task.
Route the physical handover according to the configured service model.
Maintain visibility while inventory is outside the storage location.
Approve a revised rental only after checking downstream availability.
Return receipt should begin reconciliation, not immediately restore availability. The expected inventory, quantities, components and condition need to be checked before the next reusable state is confirmed.
Late, missing, damaged or care-required inventory can remain blocked until the applicable review, charge, repair or restoration process has been completed.
Compare what came back with what the rental expected.
Route inventory through the physical work required before reuse.
Keep operational evidence connected to any financial adjustment.
Return inventory to usable stock only after the complete recovery path is finished.
The workflow protects both the commercial promise and the physical inventory throughout the complete rental lifecycle.
Define eligible inventory, duration, rates, deposits, buffers, blackout dates and extension policy.
Show only the inventory and date options appropriate to the client-facing channel.
Protect exact items, variants, quantities or kits and prevent date conflicts.
Pick, prepare, dispatch, deliver or collect and enter active-rental custody.
Verify returned inventory, quantities, components, timing and condition.
Complete care or repair, release the next available date and measure utilisation.
The module is the reusable rental engine for the client’s own channels and operations. CostumePeti is a separate marketplace destination that may be connected only where approved.
Rental Commerce controls dates, rates, reservations and rental lifecycle. Inventory and Warehouse Management controls physical locations, movement and stock execution.
The implementation should identify who approves rental values and policies, who configures the rental engine and who performs the physical work at each stage.
The correct rules depend on item type, stock model, rental duration, turnaround, delivery, condition sensitivity, account type and fulfilment model.
The final architecture depends on inventory type, duration rules, deposits, availability logic, buyer journey, fulfilment, returns, care and system connections.
No. Rental Commerce is the Commerce OS rental engine that can power a client’s own website, portal or connected channel. CostumePeti is a separate marketplace destination.
No. Rental Commerce can operate with client-owned facilities and teams. Vault operating services remain optional and separately scoped.
Yes. The configured model can support daily, weekend, weekly or other approved duration-based rate structures, including minimum and maximum periods.
Yes. Exact one-off items, variants, quantity stock, kits and component sets can use the reservation logic appropriate to their inventory model.
Availability can include the rental dates plus preparation, outbound transit, return transit, inspection, care or restoration buffers, existing commitments and blackout periods.
Yes, where configured. Holds can have an expiry and can convert into confirmed reservations or release automatically or through an approved workflow.
Potentially. The revised dates must be checked against downstream reservations, availability and any additional commercial effect before approval.
Only after return verification, quantity or component checks, condition review, required care or repair, final reinspection and the approved availability decision.
Yes, where configured and commercially permitted. The workflow can keep the physical evidence, reviewer, reason and financial adjustment connected.
Potentially. The integration depends on supported APIs, stock ownership, sync frequency, security requirements and implementation scope.
We will map duration, rates, deposits, availability, buffers, holds, reservations, checkout or assisted approval, fulfilment, extensions, returns, care, damage review, reporting and system connections.
Login