Workflows

acceptMemberInvitesWorkflow

This documentation provides a reference to the acceptMemberInvitesWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow accepts a member invitation by validating the invite token, creating a new member, updating the invite status, and linking the new member to the authentication system. Source code

Examples

API Route

packages/modules/b2c-core/src/api/vendor/invites/accept/route.ts

import {
  AuthenticatedMedusaRequest,
  MedusaResponse,
} from "@medusajs/framework";
import { ContainerRegistrationKeys } from "@medusajs/framework/utils";
import { acceptMemberInvitesWorkflow } from "../../../../workflows/seller/workflows";
import { VendorAcceptMemberInviteType } from "../validators";

export const POST = async (
  req: AuthenticatedMedusaRequest<VendorAcceptMemberInviteType>,
  res: MedusaResponse
) => {
  const query = req.scope.resolve(ContainerRegistrationKeys.QUERY);

  const { result } = await acceptMemberInvitesWorkflow(req.scope).run({
    input: {
      invite: req.validatedBody,
      authIdentityId: req.auth_context.auth_identity_id,
    },
  });

  const {
    data: [invite],
  } = await query.graph(
    {
      entity: "member_invite",
      fields: req.queryConfig.fields,
      filters: { id: result.id },
    },
    { throwIfKeyNotFound: true }
  );

  res.json({ invite });
};

Steps

validateMemberInviteStep: Validates the invite token and retrieves the invite details.
createMemberStep: Creates the new member.
updateMemberInviteStep: Marks the invite as accepted.
setAuthAppMetadataStep: Links the member to the authentication identity.

Input

input

object

required

The invite acceptance details.

Show properties

invite

AcceptMemberInviteDTO

required

The invite acceptance data.

Show properties

token

string

required

The invitation token.

name

string

required

The name of the member accepting the invitation.

authIdentityId

string

required

The ID of the authentication identity to link to the member.

Output

MemberInviteDTO

The accepted member invite.

Show properties

string

The ID of the invite.

string

The email address of the invited member.

accepted

boolean

Whether the invite has been accepted.

role

string

The role assigned to the invited member.

createOnboardingForSellerWorkflow

This documentation provides a reference to the createOnboardingForSellerWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow creates a payout onboarding flow for a seller. It validates that the seller has a payout account and then initializes the onboarding process with the payment provider. Source code

Examples

API Route

packages/modules/b2c-core/src/api/vendor/payout-account/onboarding/route.ts

import { AuthenticatedMedusaRequest, MedusaResponse } from '@medusajs/framework'
import { ContainerRegistrationKeys } from '@medusajs/framework/utils'
import { fetchSellerByAuthActorId } from '../../../../shared/infra/http/utils'
import { createOnboardingForSellerWorkflow } from '../../../../workflows/seller/workflows'
import { VendorCreateOnboardingType } from '../validators'

export const POST = async (
  req: AuthenticatedMedusaRequest<VendorCreateOnboardingType>,
  res: MedusaResponse
) => {
  const query = req.scope.resolve(ContainerRegistrationKeys.QUERY)
  const seller = await fetchSellerByAuthActorId(
    req.auth_context.actor_id,
    req.scope
  )

  const { result } = await createOnboardingForSellerWorkflow(req.scope).run({
    context: { transactionId: seller.id },
    input: {
      seller_id: seller.id,
      context: req.validatedBody.context ?? {}
    }
  })

  const {
    data: [payoutAccount]
  } = await query.graph(
    {
      entity: 'payout_account',
      fields: req.queryConfig.fields,
      filters: {
        id: result.payout_account_id
      }
    },
    { throwIfKeyNotFound: true }
  )

  res.status(200).json({
    payout_account: payoutAccount
  })
}

Steps

validatePayoutAccountExistsForSellerStep: Validates that the seller has a payout account.
createPayoutOnboardingStep: Creates the onboarding flow with the payment provider.

Input

input

object

required

The onboarding creation details.

Show properties

seller_id

string

required

The ID of the seller to create onboarding for.

context

Record<string, unknown>

required

Additional context data required by the payment provider (e.g., return URLs).

Output

OnboardingDTO

The created onboarding.

Show properties

string

The ID of the onboarding.

payout_account_id

string

The ID of the associated payout account.

data

Record<string, unknown>

Provider-specific onboarding data (e.g., onboarding URL).

context

Record<string, unknown>

The context data provided during creation.

created_at

Date

The date the onboarding was created.

updated_at

Date

The date the onboarding was last updated.

createPayoutAccountForSellerWorkflow

This documentation provides a reference to the createPayoutAccountForSellerWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow creates a payout account for a seller and links it to the seller. It validates that no payout account already exists for the seller and then creates the account with the payment provider. This workflow is idempotent. Source code

Examples

API Route

packages/modules/b2c-core/src/api/vendor/payout-account/route.ts

import { AuthenticatedMedusaRequest, MedusaResponse } from '@medusajs/framework'
import { ContainerRegistrationKeys } from '@medusajs/framework/utils'
import { fetchSellerByAuthActorId } from '../../../shared/infra/http/utils'
import {
  createPayoutAccountForSellerWorkflow,
} from '../../../workflows/seller/workflows'
import { VendorCreatePayoutAccountType } from './validators'

export const POST = async (
  req: AuthenticatedMedusaRequest<VendorCreatePayoutAccountType>,
  res: MedusaResponse
) => {
  const query = req.scope.resolve(ContainerRegistrationKeys.QUERY)
  const seller = await fetchSellerByAuthActorId(
    req.auth_context.actor_id,
    req.scope
  )

  const { result } = await createPayoutAccountForSellerWorkflow(req.scope).run({
    context: { transactionId: seller.id },
    input: {
      seller_id: seller.id,
      context: req.validatedBody.context ?? {}
    }
  })

  const {
    data: [payoutAccount]
  } = await query.graph(
    {
      entity: 'payout_account',
      fields: req.queryConfig.fields,
      filters: {
        id: result.id
      }
    },
    { throwIfKeyNotFound: true }
  )

  res.status(201).json({
    payout_account: payoutAccount
  })
}

Steps

validateNoExistingPayoutAccountForSellerStep: Validates that no payout account exists for the seller.
createPayoutAccountStep: Creates the payout account with the payment provider.
createRemoteLinkStep: Links the payout account to the seller.

Input

input

object

required

The payout account creation details.

Show properties

seller_id

string

required

The ID of the seller to create the payout account for.

context

Record<string, unknown>

required

Additional context data required by the payment provider.

Output

PayoutAccountDTO

The created payout account.

Show properties

string

The ID of the payout account.

reference_id

string

The external reference ID from the payment provider.

status

PayoutAccountStatus

The status of the payout account (pending, active, or disabled).

data

Record<string, unknown>

Provider-specific account data.

created_at

Date

The date the account was created.

updated_at

Date

The date the account was last updated.

createSellerWorkflow

This documentation provides a reference to the createSellerWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow creates a new seller in the marketplace, including creating the initial member, setting up seller onboarding, linking to authentication, and creating a default shipping profile. It exposes a sellerCreated hook for custom extensions. Source code

Steps

createSellerStep: Creates the seller record.
createMemberStep: Creates the initial member for the seller.
createSellerOnboardingStep: Creates the onboarding record.
setAuthAppMetadataStep: Links the member to the authentication identity.
createSellerShippingProfileStep: Creates a default shipping profile for the seller.

Hooks

sellerCreated: Hook that fires after a seller is created, providing the sellerId.

Input

input

object

required

The seller creation details.

Show properties

seller

CreateSellerDTO

required

The seller details.

Show properties

name

string

required

The name of the seller’s store.

description

string

A description of the seller’s store.

address_line

string

The street address of the seller.

city

string

The city of the seller.

postal_code

string

The postal code of the seller.

country_code

string

The country code of the seller.

tax_id

string

The tax ID of the seller.

photo

string

The photo URL of the seller’s store.

member

Omit<CreateMemberDTO, 'seller_id'>

required

The initial member details.

Show properties

name

string

required

The name of the member.

string

required

The email address of the member.

role

string

required

The role of the member.

auth_identity_id

string

required

The ID of the authentication identity to link to the member.

Output

SellerDTO

The created seller.

Show properties

string

The ID of the seller.

name

string

The name of the seller’s store.

handle

string

The URL-friendly handle (generated from name).

status

SellerStatus

The status of the seller (active or suspended).

created_at

Date

The date the seller was created.

updated_at

Date

The date the seller was last updated.

createVendorPromotionWorkflow

This documentation provides a reference to the createVendorPromotionWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow creates a promotion for a seller. It validates that the campaign belongs to the seller, that the target type is items only, and that all targeted products belong to the seller. Source code

Examples

API Route

packages/modules/b2c-core/src/api/vendor/promotions/route.ts

import { AuthenticatedMedusaRequest, MedusaResponse } from '@medusajs/framework'
import { ContainerRegistrationKeys } from '@medusajs/framework/utils'
import { fetchSellerByAuthActorId } from '../../../shared/infra/http/utils'
import { createVendorPromotionWorkflow } from '../../../workflows/promotions/workflows'
import { VendorCreatePromotionType } from './validators'

export const POST = async (
  req: AuthenticatedMedusaRequest<VendorCreatePromotionType>,
  res: MedusaResponse
) => {
  const query = req.scope.resolve(ContainerRegistrationKeys.QUERY)
  const seller = await fetchSellerByAuthActorId(
    req.auth_context?.actor_id,
    req.scope
  )

  const { result } = await createVendorPromotionWorkflow.run({
    container: req.scope,
    input: { promotion: req.validatedBody, seller_id: seller.id }
  })

  const {
    data: [promotion]
  } = await query.graph({
    entity: 'promotion',
    fields: req.queryConfig.fields,
    filters: {
      id: result[0].id
    }
  })

  res.status(201).json({ promotion })
}

Steps

verifyVendorCampaignStep: Validates campaign ownership.
verifyVendorPromotionStep: Validates the promotion target type.
verifyVendorTargetPromotionRulesStep: Validates product ownership in target rules.
createPromotionsWorkflow: Creates the promotion using Medusa’s core workflow.
createRemoteLinkStep: Links the promotion and campaign to the seller.

Input

input

object

required

The promotion creation details.

Show properties

promotion

CreatePromotionDTO

required

The promotion details (see createVendorPromotionWorkflow in promotions-workflows.md for full structure).

seller_id

string

required

The ID of the seller creating the promotion.

Output

PromotionDTO[]

Array containing the created promotion.

deleteMemberInvitesWorkflow

This documentation provides a reference to the deleteMemberInvitesWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow deletes a member invitation. Source code

Steps

deleteMemberInvitesStep: Deletes the member invite.

Input

string

required

The ID of the member invite to delete.

Output

This workflow does not return a value.

deleteMemberWorkflow

This documentation provides a reference to the deleteMemberWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow deletes a member from a seller’s team. Source code

Steps

deleteMemberStep: Deletes the member.

Input

string

required

The ID of the member to delete.

Output

This workflow does not return a value.

deleteSellerWorkflow

This documentation provides a reference to the deleteSellerWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow deletes a seller from the marketplace. Source code

Steps

deleteSellerStep: Deletes the seller.

Input

string

required

The ID of the seller to delete.

Output

This workflow does not return a value.

exportSellerProductsWorkflow

This documentation provides a reference to the exportSellerProductsWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow exports all products for a seller to a CSV file. It retrieves the seller’s products and generates a downloadable CSV file containing product details, variants, and pricing information. Source code

Examples

API Route

packages/modules/b2c-core/src/api/vendor/products/export/route.ts

import { AuthenticatedMedusaRequest, MedusaResponse } from '@medusajs/framework'
import { fetchSellerByAuthActorId } from '../../../../shared/infra/http/utils'
import { exportSellerProductsWorkflow } from '../../../../workflows/seller/workflows'

export const POST = async (
  req: AuthenticatedMedusaRequest,
  res: MedusaResponse
) => {
  const seller = await fetchSellerByAuthActorId(
    req.auth_context.actor_id,
    req.scope
  )

  const { result: fileData } = await exportSellerProductsWorkflow.run({
    container: req.scope,
    input: seller.id
  })

  res.json({
    url: fileData.url
  })
}

Steps

getSellerProductsStep: Retrieves all products for the seller.
generateProductCsvStep: Generates a CSV file from the product data using Medusa’s core step.
useRemoteQueryStep: Retrieves the file details including the download URL.

Input

seller_id

string

required

The ID of the seller whose products to export.

Output

FileDTO

The generated CSV file details.

Show properties

string

The ID of the file.

url

string

The download URL for the CSV file.

importSellerProductsWorkflow

This documentation provides a reference to the importSellerProductsWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow imports products from a CSV file for a seller. It parses the CSV, validates the products, creates them with “proposed” status, and emits an event to create product requests for admin approval. Source code

Examples

API Route

packages/modules/b2c-core/src/api/vendor/products/import/route.ts

import { AuthenticatedMedusaRequest, MedusaResponse } from '@medusajs/framework'
import { MedusaError } from '@medusajs/framework/utils'
import { fetchSellerByAuthActorId } from '../../../../shared/infra/http/utils'
import { importSellerProductsWorkflow } from '../../../../workflows/seller/workflows'

export const POST = async (
  req: AuthenticatedMedusaRequest,
  res: MedusaResponse
) => {
  const input = (req as any).file

  if (!input) {
    throw new MedusaError(
      MedusaError.Types.INVALID_DATA,
      'No file was uploaded for importing'
    )
  }

  const seller = await fetchSellerByAuthActorId(
    req.auth_context.actor_id,
    req.scope
  )

  const { result: products } = await importSellerProductsWorkflow.run({
    container: req.scope,
    input: {
      file_content: input.buffer.toString('utf-8'),
      seller_id: seller.id,
      submitter_id: req.auth_context.actor_id
    }
  })

  res.status(201).json({ products })
}

Steps

parseProductCsvStep: Parses the CSV file into product objects using Medusa’s core step.
validateProductsToImportStep: Validates and transforms products, setting status to “proposed”.
createProductsWorkflow: Creates the products using Medusa’s core workflow.
emitEventStep: Emits an event to trigger product request creation.

Input

input

object

required

The product import details.

Show properties

file_content

string

required

The CSV file content as a string.

seller_id

string

required

The ID of the seller importing products.

submitter_id

string

required

The ID of the member submitting the import.

Output

ProductDTO[]

Array of created products (in proposed status).

inviteMemberWorkflow

This documentation provides a reference to the inviteMemberWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow creates a member invitation for a seller’s team. Source code

Examples

API Route

packages/modules/b2c-core/src/api/vendor/invites/route.ts

import {
  AuthenticatedMedusaRequest,
  MedusaResponse,
} from "@medusajs/framework";
import { ContainerRegistrationKeys } from "@medusajs/framework/utils";
import { fetchSellerByAuthActorId } from "../../../shared/infra/http/utils";
import { inviteMemberWorkflow } from "../../../workflows/seller/workflows";
import { VendorInviteMemberType } from "./validators";

export const POST = async (
  req: AuthenticatedMedusaRequest<VendorInviteMemberType>,
  res: MedusaResponse
) => {
  const query = req.scope.resolve(ContainerRegistrationKeys.QUERY);

  const seller = await fetchSellerByAuthActorId(
    req.auth_context.actor_id,
    req.scope,
    ["id", "name"]
  );

  const { result: created } = await inviteMemberWorkflow(req.scope).run({
    input: {
      ...req.validatedBody,
      seller_id: seller.id,
    },
  });

  // ... query invite and emit event

  res.status(201).json({ invite });
};

Steps

createMemberInviteStep: Creates the member invitation.

Input

input

CreateMemberInviteDTO

required

The invitation details.

Show properties

seller_id

string

required

The ID of the seller creating the invitation.

string

required

The email address of the person to invite.

role

string

required

The role to assign to the invited member.

Output

MemberInviteDTO

The created member invitation.

Show properties

string

The ID of the invitation.

string

The email address of the invited person.

token

string

The unique invitation token.

role

string

The role assigned to the invitation.

seller_id

string

The ID of the seller who created the invitation.

accepted

boolean

Whether the invitation has been accepted.

inviteSellerWorkflow

This documentation provides a reference to the inviteSellerWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow sends an invitation email to a potential seller to join the marketplace platform. Source code

Examples

API Route

packages/modules/b2c-core/src/api/admin/sellers/invite/route.ts

import { MedusaRequest, MedusaResponse } from '@medusajs/framework'
import { inviteSellerWorkflow } from '../../../../workflows/seller/workflows'
import { AdminInviteSellerType } from '../validators'

export async function POST(
  req: MedusaRequest<AdminInviteSellerType>,
  res: MedusaResponse
): Promise<void> {
  const { result: invitation } = await inviteSellerWorkflow.run({
    container: req.scope,
    input: req.validatedBody
  })

  res.status(201).json({ invitation })
}

Steps

sendSellerInvitationEmailStep: Sends the invitation email.

Input

input

CreateSellerInvitationDTO

required

The invitation details.

Show properties

string

required

The email address to send the invitation to.

registration_url

string

The registration URL to include in the invitation email.

Output

NotificationDTO

The notification details for the sent invitation email.

recalculateOnboardingWorkflow

This documentation provides a reference to the recalculateOnboardingWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow recalculates a seller’s onboarding status by checking various completion criteria including store information, products added, shipping locations configured, and Stripe connection established. Source code

Examples

API Route

packages/modules/b2c-core/src/api/vendor/sellers/me/onboarding/route.ts

import { AuthenticatedMedusaRequest, MedusaResponse } from '@medusajs/framework'
import { ContainerRegistrationKeys } from '@medusajs/framework/utils'
import { fetchSellerByAuthActorId } from '../../../../../shared/infra/http/utils'
import { recalculateOnboardingWorkflow } from '../../../../../workflows/seller/workflows'

export const POST = async (
  req: AuthenticatedMedusaRequest,
  res: MedusaResponse
) => {
  const query = req.scope.resolve(ContainerRegistrationKeys.QUERY)
  const seller = await fetchSellerByAuthActorId(
    req.auth_context.actor_id,
    req.scope
  )

  await recalculateOnboardingWorkflow.run({
    container: req.scope,
    input: seller.id
  })

  const {
    data: [onboarding]
  } = await query.graph({
    entity: 'seller_onboarding',
    fields: req.queryConfig.fields,
    filters: {
      seller_id: seller.id
    }
  })

  res.json({ onboarding })
}

Steps

recalculateOnboardingStep: Recalculates and updates the onboarding status.

Input

seller_id

string

required

The ID of the seller to recalculate onboarding for.

Output

SellerOnboardingDTO

The updated onboarding status.

Show properties

string

The ID of the onboarding record.

seller_id

string

The ID of the seller.

store_information

boolean

Whether store information is complete.

products

boolean

Whether products have been added.

locations_shipping

boolean

Whether shipping locations are configured.

stripe_connection

boolean

Whether Stripe connection is established.

syncStripeAccountWorkflow

This documentation provides a reference to the syncStripeAccountWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow synchronizes the status of a payout account with the payment provider (Stripe Connect). It retrieves the latest account status from the provider and updates the local record. Source code

Examples

API Route

packages/modules/b2c-core/src/api/vendor/payout-account/route.ts

import { syncStripeAccountWorkflow } from '../../../workflows/seller/workflows'

// Inside GET handler
if (payout_account.status !== 'active') {
  await syncStripeAccountWorkflow.run({
    container: req.scope,
    input: payout_account.id
  })

  // Refresh payout account data
}

Steps

syncStripeAccountStep: Synchronizes the account status with Stripe.

Input

account_id

string

required

The ID of the payout account to synchronize.

Output

PayoutAccountDTO

The synchronized payout account.

updateMemberWorkflow

This documentation provides a reference to the updateMemberWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow updates a member’s details. Source code

Steps

updateMemberStep: Updates the member.

Input

input

UpdateMemberDTO

required

The member update details.

Show properties

string

required

The ID of the member to update.

name

string

The new name.

role

string

The new role.

Output

MemberDTO

The updated member.

updateSellerWorkflow

This documentation provides a reference to the updateSellerWorkflow. It belongs to the @mercurjs/b2c-core package. This workflow updates a seller’s details. Source code

Examples

API Route

packages/modules/b2c-core/src/api/vendor/sellers/me/route.ts

import { AuthenticatedMedusaRequest, MedusaResponse } from '@medusajs/framework'
import { ContainerRegistrationKeys } from '@medusajs/framework/utils'
import { fetchSellerByAuthActorId } from '../../../../shared/infra/http/utils/seller'
import { updateSellerWorkflow } from '../../../../workflows/seller/workflows'
import { VendorUpdateSellerType } from '../validators'

export const POST = async (
  req: AuthenticatedMedusaRequest<VendorUpdateSellerType>,
  res: MedusaResponse
) => {
  const query = req.scope.resolve(ContainerRegistrationKeys.QUERY)
  const { id } = await fetchSellerByAuthActorId(
    req.auth_context.actor_id,
    req.scope
  )

  await updateSellerWorkflow(req.scope).run({
    input: {
      id,
      ...req.validatedBody
    }
  })

  const {
    data: [seller]
  } = await query.graph(
    {
      entity: 'seller',
      fields: req.queryConfig.fields,
      filters: { id }
    },
    { throwIfKeyNotFound: true }
  )

  res.json({ seller })
}

Steps

updateSellerStep: Updates the seller.

Input

input

UpdateSellerDTO

required

The seller update details.

Show properties

string

required

The ID of the seller to update.

name

string

The new name.

description

string

The new description.

address_line

string

The new address line.

city

string

The new city.

postal_code

string

The new postal code.

country_code

string

The new country code.

tax_id

string

The new tax ID.

photo

string

The new photo URL.

status

SellerStatus

The new status (active or suspended).

Output

SellerDTO

This step does not return a value.

createSellerStep

Creates a seller record. It automatically generates a URL-friendly handle from the seller name. If an error occurs after creation, the step’s compensation function automatically deletes the created seller. Source code

Input

input

CreateSellerDTO

required

The seller details.

Output

The ID of the seller whose products to retrieve.

Output

ProductDTO[]

Array of products with full details including variants, prices, options, tags, and images.

recalculateOnboardingStep

Recalculates a seller’s onboarding status by checking multiple completion criteria:

Store information completeness (name, address, tax ID, etc.)
Products added
Shipping locations configured
Stripe connection established

Updates a member invitation, typically to mark it as accepted. Source code

Input

input

object

required

Show properties

string

Validates that a seller has a payout account. Throws an error if no payout account exists and returns the payout account ID if found. Source code

Input

sellerId

string

required

The ID of the seller to check.

Output

object

Show properties

string

The ID of the payout account.

validateProductsToImportStep

Validates products from a CSV import, parses them according to the product schema, and sets their status to “proposed” for admin approval. Source code

Input

products

unknown[]

required

Array of product objects parsed from CSV.

Output

CreateProductDTO[]

Array of validated product creation DTOs with status set to “proposed”.

verifyVendorCampaignStep

Validates that a campaign belongs to the seller. If no campaign is specified, the validation is skipped. Source code

Input

input

object

required

Show properties

promotion

object

required

The promotion data.

Show properties

campaign_id

string

The ID of the campaign to verify.

seller_id

string

required

The ID of the seller.

Output

void

Throws an INVALID_DATA error if the campaign doesn’t belong to the seller.

verifyVendorPromotionStep

Validates that a vendor promotion uses the correct target type. Vendor promotions must target items only. Source code

Input

input

object

required

Show properties

promotion

CreatePromotionDTO

required

The promotion data to validate.

seller_id

string

required

The ID of the seller.

Output

void

Throws an INVALID_DATA error if target_type is not “items”.

verifyVendorTargetPromotionRulesStep

Validates that target promotion rules only use the allowed attribute (items.product.id) and that all targeted products belong to the seller. Source code

Input

input

object

required

Show properties

rules

CreatePromotionRuleDTO[]

Array of target rules to validate.

seller_id

string

required

The ID of the seller.

Output

void

Throws an INVALID_DATA error if:

Rules use attributes other than “items.product.id”
Any targeted product doesn’t belong to the seller

Quick start

Components

Core Concepts

Product

Integrations

Deployment

Help

​Workflows

​acceptMemberInvitesWorkflow

​Examples

​Steps

​Input

​Output

​createOnboardingForSellerWorkflow

​Examples

​Steps

​Input

​Output

​createPayoutAccountForSellerWorkflow

​Examples

​Steps

​Input

​Output

​createSellerWorkflow

​Steps

​Hooks

​Input

​Output

​createVendorPromotionWorkflow

​Examples

​Steps

​Input

​Output

​deleteMemberInvitesWorkflow

​Steps

​Input

​Output

​deleteMemberWorkflow

​Steps

​Input

​Output

​deleteSellerWorkflow

​Steps

​Input

​Output

​exportSellerProductsWorkflow

​Examples

​Steps

​Input

​Output

​importSellerProductsWorkflow

​Examples

​Steps

​Input

​Output

​inviteMemberWorkflow

​Examples

​Steps

​Input

​Output

​inviteSellerWorkflow

​Examples

​Steps

​Input

​Output

​recalculateOnboardingWorkflow

​Examples

​Steps

​Input

​Output

​syncStripeAccountWorkflow

​Examples

​Steps

​Input

​Output

​updateMemberWorkflow

​Steps

​Input

​Output

​updateSellerWorkflow

Workflows

acceptMemberInvitesWorkflow

Examples

Steps

Input

Output

createOnboardingForSellerWorkflow

Examples

Steps

Input

Output

createPayoutAccountForSellerWorkflow

Examples

Steps

Input

Output

createSellerWorkflow

Steps

Hooks

Input

Output

createVendorPromotionWorkflow

Examples

Steps

Input

Output

deleteMemberInvitesWorkflow

Steps

Input

Output

deleteMemberWorkflow

Steps

Input

Output

deleteSellerWorkflow

Steps

Input

Output

exportSellerProductsWorkflow

Examples

Steps

Input

Output

importSellerProductsWorkflow

Examples

Steps

Input

Output

inviteMemberWorkflow

Examples

Steps

Input

Output

inviteSellerWorkflow

Examples

Steps

Input

Output

recalculateOnboardingWorkflow

Examples

Steps

Input

Output

syncStripeAccountWorkflow

Examples

Steps

Input

Output

updateMemberWorkflow

Steps

Input

Output

updateSellerWorkflow

Examples

Steps

Input

Output

Steps

createMemberInviteStep

Input