Both are supported. Reverb shops can export listings as CSV and SleekRank reads that file. Shops that maintain a trade-in sheet can share read-only with the SleekRank service account and SleekRank pulls on each cache refresh.

Include stock or intake number in the slug. The example strymon-timeline-stock-7211 uses brand, model, and stock so multiple identical pedals coexist on the site. The sheet needs a stable identifier column for the slug to be deterministic.

Firmware version is a column in the row. Map it to a selector and the template renders it in the spec table. Pedals without updatable firmware leave the column blank and the template hides the row conditionally via a selector mapping rule.

Shipping is destination-specific, so the page renders a shipping calculator block in WordPress rather than a static figure. The block reads pedal weight and dimensions from the row via a selector mapping and calls a shipping API client-side.

Accessories is a list column in the row. Map it via a list mapping that injects accessory names into a bullet list in the WordPress template. Each pedal can show a different accessory bundle without any per-pedal hand editing in the editor.

Yes if the row carries required Product fields. Map slug, name, image, brand, condition, offers price, and offers priceCurrency. The rich results test flags any missing fields so the shop patches the sheet rather than the template per pedal.

Yes. Add a status column with values available and sold. Configure the page group to render sold rows with a sold-badge variant via a conditional selector. The URL stays indexed, the schema price clears, and a sold tag appears in the listing.

Add a status column. Filter the page group on status equals available. Pedals in bench check stay in the sheet but do not render URLs. When the bench check passes, the next cache refresh creates the page automatically without staff intervention.