medusajs/medusa · critical · Error

Unable to retrieve the fulfillment provider with id: ${provi

Error message

Unable to retrieve the fulfillment provider with id: ${providerId}, the following error occurred: ${err.message}

What it means

Generic wrapper thrown when resolving a fulfillment provider from the container fails with a non-registration error (any exception other than AwilixResolutionError). The original error message is included and logged; the cause is inside the provider module or its initialization.

Source

Thrown at packages/modules/fulfillment/src/services/fulfillment-provider.ts:79

  ): FulfillmentTypes.IFulfillmentProvider {
    try {
      return this.__container__[`fp_${providerId}`]
    } catch (err) {
      if (err.name === "AwilixResolutionError") {
        const errMessage = `
Unable to retrieve the fulfillment provider with id: ${providerId}
Please make sure that the provider is registered in the container and it is configured correctly in your project configuration file.`

        // Log full error for debugging
        this.#logger.error(`AwilixResolutionError: ${err.message}`, err)

        throw new Error(errMessage)
      }

      const errMessage = `Unable to retrieve the fulfillment provider with id: ${providerId}, the following error occurred: ${err.message}`
      this.#logger.error(errMessage)

      throw new Error(errMessage)
    }
  }

  async listFulfillmentOptions(providerIds: string[]): Promise<any[]> {
    return await promiseAll(
      providerIds.map(async (p) => {
        const provider = this.retrieveProviderRegistration(p)
        return {
          provider_id: p,
          options: (await provider.getFulfillmentOptions()) as Record<
            string,
            unknown
          >[],
        }
      })
    )
  }

View on GitHub (pinned to 5e06e544a2)

Solutions

Read the appended err.message and the server log line — it names the true cause
Fix the provider code/dependency issue it indicates
Rebuild/reinstall the provider package and restart

Defensive patterns

Strategy: try-catch

Try / catch

try { const provider = await fulfillmentProviderService.retrieveProviderRegistration(id) } catch (e) { logger.error(e.message); // message embeds the root cause — act on it throw e }

Prevention

Add tests that import each provider module to catch evaluation errors early
Keep provider dependency versions in sync with the host app

When it happens

Trigger: A provider plugin throws during module evaluation/import (syntax error, missing dependency) or its container activation fails while retrieving it for a shipping option.

Common situations: Broken provider build output, missing peer dependency in the provider package, or a runtime error in the provider constructor.

Related errors

AI-assisted analysis of medusajs/medusa@5e06e544a2 (2026-08-27). Data as JSON: /api/errors/23e7c9447b426919. Report an issue: GitHub.