Medusa

In Admin, create simple products or variants and configure multi-part products or bundles with inventory kits. The creation form moves through details, organization and variants, with an optional kit step. Assign each product to the intended sales channel and check that it appears in the storefront.

Sales channels can represent a web storefront, mobile app or another selling context. They scope which products buyers see and associate orders, stock locations and shipping options with the channel. This gives teams different catalog and fulfillment paths, but each channel must be configured and tested.

The Inventory area tracks items and quantities across locations and reservations. Inventory items can be linked to variants, including those used in bundles. Check stock and reservation behavior across every sales channel before taking live orders.

The Orders area brings together orders from different channels, with payment and fulfillment status. Staff can capture payments, create shipments and fulfillments, and handle returns or exchanges. The actual payment provider and fulfillment path need configuration.

Fulfillment can cover an entire order or separate item groups, followed by a shipment with a tracking number and delivery status. Returns may be requested through an implemented storefront flow or created by an admin, then received and refunded. Rehearse exceptions with sample orders before relying on that process.

Regions control currencies, payment providers and fulfillment providers. Tax regions and inclusive or exclusive pricing settings affect checkout totals. Verify the correct country and subregion rates and available methods with test carts for every market served.

Payment Module Providers connect services such as Stripe for authorization, capture and refunds. Medusa also includes a system provider that records a payment method without processing funds. Test the configured provider and reconcile a real processor result separately from an order marked paid in a test flow.

A storefront is a separate application from the Medusa server and Admin. Developers can build one or adapt the Next.js starter and call the Store API. Allow time to implement checkout, customer-facing returns, design and deployment rather than assuming the backend alone is a finished storefront.