Let customers save their garage and shop parts that fit
Let shoppers save their vehicles instead of entering the same details each visit. Connect their selected vehicle to your existing compatibility and product filtering tools.
Installs from the Shopify App Store · Then US$29.99/month per store, billed through Shopify
A custom experience, built by you or your developer.
Illustration: Jamie’s saved garage with two vehicles, a 2024 Rivian R1S and a 2025 Lucid Gravity.
Illustrative storefront · Your design, your brand
Fitment starts with a vehicle the store can remember
An auto-parts customer should not have to choose the same year, make, model, and trim on every visit.
The store built a My Garage feature and saved each customer’s vehicles as structured data on the Shopify customer. The theme can load the selected vehicle during later sessions and use the merchant's fitment data to guide the product experience.
FieldsRaven stored the garage. The merchant’s catalog and theme logic still decide which parts fit each vehicle.
A garage that follows the customer across devices.
Garage records in one implementation
A FieldsRaven processing-record count, not a count of unique customers.
Garage records in another
A second deployment used the same saved-vehicle pattern with its own merchant-defined shape.
16,000+ garage records in one implementation and 22,000+ in another. They are record counts, not unique customers. The garage can follow a customer across sessions and devices, while the merchant theme uses its own fitment source to decide what fits.
Historical implementation results from the existing FieldsRaven use-case story.
Make it feel like
part of your store.
Start with the recipe and code generated for your field. Adapt the interface, connect it, then test the full experience.
Configure your field
Choose the customer resource and the data your experience needs to save.
Connect your storefront
Use your field’s Get Code output and the recipe to connect your custom interface.
Test the complete journey
Confirm the saved value in Shopify and test returning to it as a signed-in customer.
Connect Codex, Claude Code, or Cursor through FieldsRaven MCP to configure fields, retrieve starter code, and check saved submissions.
Connect your coding tool ↗View starter code
Scroll sideways to see more code
const cfg = window.FR_CUSTOM__CUSTOMER_VEHICLE_GARAGE;
const payload = {
selected_id: "vehicle-1042",
vehicles: [{ id: "vehicle-1042", year: "2022", make: "Volvo", model: "XC60" }]
};
await fetch("/apps/raven/create_metafield", {
method: "PUT",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
raven: {
raven_id: cfg.ravenId,
resource_id: cfg.resourceId,
raven_mac: cfg.ravenMac,
value: JSON.stringify(payload)
}
})
});Run this request from a validated add, edit, remove, or select handler. Do not run it on page load.
A JSON save replaces the full metafield value. Read the current garage, apply the change, and send the full updated object.
Get Code supplies the configuration and inline HMAC. The complete recipe covers labeled fields, stable IDs, the empty state, and selected-vehicle updates.
Custom storefront design, integration, and testing are still required.
Does FieldsRaven provide fitment data?
No. FieldsRaven stores the customer’s saved vehicles. Your fitment system supplies the compatibility rules.
Can a customer save several vehicles?
Yes. The JSON value can contain a vehicle list and a separate selected vehicle ID.
Can support see the garage?
The saved value lives on the Shopify customer, so an authorized team member can inspect it in Shopify admin.
Can I use a simpler data shape?
Yes. Choose a data shape that matches the fitment code your storefront already uses.