Medusa Storefront Development FAQs

Question 1

Why should I use the Medusa SDK instead of a standard fetch request?

Accepted Answer

The Medusa SDK automatically injects required headers like the publishable API key for store routes and authentication headers for admin routes, preventing common authorization errors.

Question 2

How does this skill handle price formatting in Medusa?

Accepted Answer

It enforces a critical rule: prices from Medusa are stored as-is (e.g., 49.99). You should display them directly and never divide by 100, which is a common mistake in other platforms.

Question 3

Does this skill work with custom API routes?

Accepted Answer

Yes, it provides specific patterns for using sdk.client.fetch() to call custom endpoints while still benefiting from the SDK's automatic header management and serialization.

Question 4

Can I use this for state management?

Accepted Answer

Yes, it includes advanced React Query patterns for handling loading states, hierarchical query keys for cache management, and invalidation strategies after mutations.

Question 5

Why shouldn't I use JSON.stringify() with the SDK?

Accepted Answer

The Medusa SDK handles JSON serialization automatically. Using JSON.stringify() on the body parameter causes double-serialization, which prevents the server from parsing the request correctly.

Medusa Storefront Development

Características Principales

Casos de Uso

ordercli Food Delivery Manager

Reverse Logistics & Returns Manager

Finance & Billing Operations