• Requirements
  • Limitations
  • Proxy routes to the online store

Adopt Hydrogen incrementally

Some merchants may prefer to adopt the Hydrogen storefront incrementally. For instance, they might want to initially create their product pages in Hydrogen while continuing to serve other pages with Liquid during the migration process.

To achieve this in Hydrogen, you can programmatically proxy your Liquid online store routes to be served by your Hydrogen app on a request-by-request basis.

Note

Oxygen doesn't support proxies in front of your Oxygen deployments. A proxy might conflict with Oxygen's bot mitigation systems and may cause SEO issues. Requests should go to Oxygen, and any proxies to the online store should be done through Hydrogen.

Requirements

Anchor link to section titled "Requirements"
  • You've completed your Hydrogen build and your Hydrogen storefront is ready for launch.

Limitations

Anchor link to section titled "Limitations"
  • Incremental adoption is only supported with Oxygen.
  • Customer sessions can't be shared between the online store and the Hydrogen storefront without using Multipass.

Proxy routes to the online store

Anchor link to section titled "Proxy routes to the online store"

Caution

This is an advanced tutorial and is not supported by Shopify. Some Shopify features, such as Shopify analytics, may not work as expected. Proxying requests to the online store might also result in increased latency for proxied pages. Because of this, we recommend migrating as much as possible to your Hydrogen app.

You can leverage Remix's catch-all route (app/routes/$.jsx) to fall back to the Online Store by default, or handle each route individually in the appropriate file (e.g., app/routes/products/$handle.jsx).

Here's an example of how to create a catch-all proxy route:

On this page

  • Requirements
  • Limitations
  • Proxy routes to the online store