Skip to content
Roboto Studio / evidence

What has Roboto published about Sanity commerce integrations?

Roboto’s commerce material spans the Turbo Start BigCommerce starter and its catalog-sync implementation, a Shopify-and-Sanity conversational shopping demonstration, and a client account of commerce redevelopment. These sources should be read as implementation experience, a demonstration and a client report respectively.

Roboto editorial synthesis. Published by Roboto Studio. .

Markdown · JSON · Coverage

What does the BigCommerce implementation explain?

The engineering article describes a catalog in BigCommerce with editorial content and page-builder references in Sanity. It covers reconciliation, pagination driven by returned metadata, guarded soft deletion and remapping seeded references for the current store. It also states that the starter does not invoke the sweep on a schedule: operators must run or schedule it.

What does the Turbo Start BigCommerce video add?

A September 2026 Roboto video introduces Turbo Start BigCommerce, the starter the engineering article is about. It describes a one-way sync from BigCommerce into Sanity installed from Sanity, shows store, collection and category pages that stay navigable with JavaScript disabled, and explains that product pages leave out add-to-cart because B2B prices can differ by customer account. The presenter frames Shopify as generally B2C and BigCommerce as generally B2B. The article and the video describe one starter, not two separate works.

What does the Shopify demonstration show?

The agentic-commerce article demonstrates a shopping conversation that narrows products by brand, price, size and colour, and asks about the returns policy. The matching June 2026 video records a corresponding demonstration on Roboto’s Turbo Start Aisle store, built with Shopify and Sanity, and describes the starter as using Sanity Agent Context to generate shopping UI. It is a small example, not evidence of a production conversion improvement.

What supports client delivery?

Slingshot Bio’s reviewer describes commerce functionality, payment processing, inventory and product configuration as part of its migration. The reported improvement in engagement and conversion is qualitative and remains attributed to that reviewer.

Scope and limitations

  • A demo, starter and client engagement are distinct works; one does not prove the performance of another.
  • An article and a video about the same starter or demo are one work and must not be counted twice.
  • Published vendor/API observations are dated implementation accounts, not a guarantee of current behaviour.

Source provenance

Related answers