SEED

plan.json is plain data — write it from the brief. Default to 3–4 rentals across one or two resource types (the seed shows the shape; the owner adds the rest in the dashboard) and make them exercise the UI: one hourly and one daily rental when the business allows it, a free or approval-gated one where it fits, and an image per rental — the default is an imagePrompt (AI-generated, ~1 Wix AI credit per image, account-billed): brand-contextual — subject, aesthetic/mood, palette, lighting — always ending “no text, no watermarks”. At least one image shows the real thing being rented. For an asset the user actually supplied use imageMediaId (a file already in the site’s Media Manager, such as one the user uploaded there: used as it is, no copy; a static.wixstatic.com/media/<file id> URL of a site file counts as one), imagePath (a file on this machine — uploaded to Wix Media) or imageUrl (their own hosted URL; verify it with curl -sI → 200) — never a stock-photo or guessed URL. Images resolve in parallel and never block the seed.

• resourceTypes — the kinds of things rented (name, max 40 characters, unique per site) and the individual units in each (resources, by name). Two resources in a type mean two customers can rent in parallel. Resources are created without working hours: bookable around the clock, which keeps a multi-day rental to one booking. Opening hours are dashboard work — say so.
• rentals — one entry per rental service. resourceType names the type it rents from (every resource of that type unless resources narrows it). The rate lives on the service, so resources that rent at different prices are separate rentals sharing a type.
  • unit — HOUR or DAY, never both on one rental (a room by the hour AND by the day is two rentals). min/max are in that unit: hours from 0.5 to 24 (default 1 to 8), days from 1 to 8 (default 1 to 5).
  • rate — a number per unit (per hour or per day); Wix multiplies it out at booking time. Omit it or set free: true for a no-fee rental (rents without a checkout, paid in person).
  • requireManualApproval: true — rentals are requests the owner approves (the CTA reads “Request to rent”).
• currency — 3-letter ISO code at the top of the plan, set only when the brief names one: a sentence about currency, or a price written with its unit (“9 dollars”, “$9”, “€20”). Do not infer it from a language, a country, or an address. The seed sets the site to it before creating anything, because rates are stored in the site currency at create time; a new site starts in the currency of the account that created it, not the business’s.

The result carries durationRangeConfirmed (the first rental re-read; "HOUR"/"DAY" means the range landed, null means it was dropped and the rental would book as a fixed slot — stop and read the create-service reference), the created rentals with their slugs, the resource types with their resources, preexisting[] (rentals the site already listed, see below), errors per rental, and dashboardUrl.

Seeding is additive — the seed never deletes or overwrites anything on the site, and neither do you. There is no cleanup flag and no cleanup step. The Rentals install adds its own sample rental to a new site (“Conference room”, $45 an hour, 1 to 8 hours), and the live listing shows it next to the owner’s rentals, so it is never silent: the result’s preexisting[] names every rental the run did not create and the plan did not name ({ id, name, slug }), and the closing message says so with the Rentals dashboard link (dashboardUrl in the result) so the owner removes it there if they want to. Resource types and resources are idempotent by name — a re-run reuses “Kayaks” instead of creating a second one.

Supplied content

The general rules are in templates/shared/SUPPLIED-CONTENT.md. For rentals, each thing the user rents out is one entry. Its name becomes name; “per hour”/”per day” (or a price written that way) becomes unit and rate; a stated shortest or longest rental becomes min/max; the number of units they own becomes that type’s resources (named “Kayak 1”, “Kayak 2” when the user gives no names); a group name (“boats”, “rooms”) becomes the resourceType. Their photo becomes imageUrl. A rental with no unit is a question for the user.

Escape hatch — individual functions

setupRentals composes exported steps — installRentalsApp, createResourceTypes, createResources, buildRental, createRental, confirmDurationRange, readRentals, importImage, attachRentalImage, plus makeCtx() — import them only for a partial re-seed.

Reference

Unexpected shape or an uncovered operation → read the live Wix API reference; every call the script makes carries a docs: line with its reference page. The Rentals model itself is four pages under https://dev.wix.com/docs/api-reference/business-solutions/rentals/.