You can use Airtable and miniExtensions to let customers browse rental equipment and submit an inquiry with dates, quantities and intended use. Keep the request separate from a confirmed reservation so staff can check actual availability, suitability and turnaround time before offering equipment.
This workflow fits a small equipment hire team that receives vague messages such as “Do you have a projector next Friday?” The goal is a complete, equipment-linked inquiry, not automatic booking, deposit collection or conflict-free stock allocation. The example uses fictional Harbor Event Hire and ordinary presentation equipment.
Separate the catalog from individual rental units
A customer usually wants a type of equipment, while staff needs to know which physical unit can fulfill the request. Publish a catalog item called Portable Projector Kit, then keep serial numbers, maintenance notes and individual unit availability in staff-managed records.
Do not display “four available” merely because four units exist. One may be under inspection, another due back late and a third already promised for the requested period. Start with “Request availability” and have staff confirm the dates. This avoids asking a simple catalog view to behave like a specialized rental inventory engine.
Build the request model
- Equipment types: Public name as primary text; Category as single select; Description as long text; Public photo as attachment; Included accessories as long text; Published as checkbox; Public reference as single-line text.
- Rental inquiries: Inquiry reference as primary text; Contact name as text; Email as email; Requested pickup and Requested return as dates with time; Intended use as long text; Inquiry state as single select; Staff response as long text; Received at as created time.
- Inquiry lines: Line reference as primary text; Inquiry and Equipment type as links; Requested quantity as an integer number; Accessory request as long text; Staff-confirmed quantity as number.
- Units and reservations: Staff-only tables holding unit identifiers, condition, confirmed time windows and the relevant inquiry link. Define these according to the team’s actual operational process.
For a minimal first version, add Equipment type as a linked-record field, Requested quantity as an integer number and Staff-confirmed quantity as a number directly to Rental inquiries. Accept one equipment type per inquiry and omit Inquiry lines. When multi-item requests become necessary, move those item-level fields into the linked Inquiry lines table and review how the new form creates each line. The simpler form reduces setup work. Do not claim that a complex multi-line flow has been configured merely because the proposed tables exist.
Make public browsing useful without exposing operations
Create an Airtable view filtered to Published being checked, and review its records as the approved public catalog. Configure the miniExtensions Interface to use that filtered view; verify that an unchecked item cannot appear in browsing or the inquiry picker. Create the Interface for this approved catalog. Unlike a personal Portal, an Interface without login shows the same configured data to its visitors; see the Interface setup guide. Keep inquiries, unit identifiers, customer details and staff reservations out of that public extension.
Use Gallery for equipment photos or List for compact specifications. Configure public preview fields and inspect the expanding form separately. The preview-field documentation describes these distinct display settings. A customer needs the model’s practical characteristics and included accessories, not internal cost or private condition notes.
Group the approved items by useful categories such as Presentation, Audio and Lighting. Review the catalog copy for claims staff can support. A photograph and a general description cannot guarantee that a projector will work in a particular room or with every laptop connection.
Collect the dates and the equipment choice
Build a separate inquiry Form with contact details, equipment type, quantity, pickup/return times and intended use. Make the choice explicit through an existing Equipment types linked-record field. Prevent customers from adding or editing catalog records through the picker or its expanded form.
For the example, a customer requests two Portable Projector Kits from Friday afternoon to Monday morning for two meeting rooms. Ask about the connection or accessory requirement in plain language. Staff can then check whether the requested kit includes the appropriate cables without presenting an unchecked compatibility assumption as a guarantee.
Explain the time zone and whether the requested return time includes collection. Staff should flag reversed dates and non-positive quantities before reviewing availability. If you implement cross-field date validation, follow the documented formula and Save & Continue approach; simply displaying two date inputs does not enforce an end-after-start rule.
Confirm a reservation through a human review
Staff reads the inquiry, checks existing commitments, expected return condition and preparation time, then identifies suitable units. Record a clear response: both kits available as requested, one kit available, or an alternative suggested. Do not change the customer-requested quantity to hide a partial offer; use the separate confirmed quantity.
Only create the confirmed reservation after the customer and staff have completed the team’s actual confirmation process. Terms, payment, deposits and collection arrangements remain separate. A submitted inquiry, a status change or a displayed calendar does not itself execute those steps.
If another customer requests the same units while the first inquiry is pending, keep both requests visible for staff review. This design makes no atomic locking or double-booking prevention claim. A busy rental business may need a dedicated booking system for that requirement.
Handle substitutions and the handoff to checkout
Suppose one projector is returned damaged. Staff records the changed availability, checks a substitute model and contacts the customer about the difference. Keep the originally requested type in the inquiry and identify the proposed alternative separately. Do not silently replace it with an item that has different capabilities.
After confirmation, the team moves to its equipment checkout and return process. That operational handoff is distinct from inquiry intake. It should identify the actual units, accessories and return arrangement rather than treating the catalog request as evidence that equipment was collected.
Test a full inquiry before sharing the catalog
Use fictional data to test a single-item request, a multi-item request if enabled, reversed dates, a partial quantity offer and a substitution. Check that public visitors cannot browse prior inquiries or staff reservations, and that linked-record expansion reveals only approved catalog details. Verify saved values in Airtable after reload.
Publish the reviewed extension configuration and use its real end-user URL, as described in the sharing documentation. This article proposes a workflow and acceptance checks, not observed runtime results. The practical outcome is better information for the rental team to confirm a reservation, with the limits of a request form kept clear.
