Let customers save a custom rug and return later
Let signed-in shoppers name and save a custom design with their selected options, then return to it on another visit.
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: a saved rug design, a Sage diamond rug in 8 × 10, in the shopper’s account.
Illustrative storefront · Your design, your brand
Customers needed to see a rug before they would buy it
Fibreworks and Solidago built custom rugs for customers who needed to see a design before they could buy. The team needed a way to keep those designs in customer accounts.
They created a JSON customer metafield and connected the rug builder to it, keeping the product and merchant-defined choices together for a future visit.
Customers can save rug designs and favorite products to their accounts. The theme owns the designer and the code that reopens a saved configuration later.
Saved designs, stored on the customer record in Shopify.
Saved-design submissions processed
FieldsRaven processing rows from the storefront rug builder, not a claim that each save was a distinct design.
Saved-recipe records processed
A second unnamed implementation used the same customer-owned pattern for related saved records.
28,000+ saved-design submissions processed, alongside 125,000+ saved-recipe records processed in another implementation. Neither result counts distinct designs. The customer can pause and reopen merchant-defined options later, while the theme decides how to continue the design.
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_SAVED_CONFIGURATIONS;
const payload = [{
id: "design-1042",
name: "Living room rug",
product_handle: "custom-wool-rug",
options: { size: "8x10", border: "linen" }
}];
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 create, update, or delete handler. Do not run it on page load.
A JSON save replaces the full metafield value. Read the current saved configurations, apply the change, and send the complete updated list.
Get Code supplies the configuration and inline HMAC. The complete recipe covers stable IDs plus create, update, reopen, and remove behavior.
Custom storefront design, integration, and testing are still required.
Does FieldsRaven build the configurator?
No. Your theme or product-builder code controls the design interface; FieldsRaven accepts the resulting customer value.
What can the JSON contain?
Use the values needed to rebuild the design, such as product, size, material, color, border, quantity, and a stable design ID.
Can a customer keep several designs?
Yes. Store a list of design objects and update that complete list when the customer saves or deletes one.
Will the design follow the customer to another device?
Yes, after the value is saved to the Shopify customer and the shopper signs in on the other device.