OMS Support for Multiple Stores

chord supports a "multi store" architecture within the chord oms, i e sending data from more than one store to the same chord instance multiple stores can be used to delineate between a d2c or wholesales business or to create locale specific stores that require a specific product catalog or stores that are specific to a certain country or region this is an advanced feature please speak with someone at chord before acting on the following chord does not currently support multiple currencies a store can be assigned to the following entities orders subscriptions (the store assigned to the subscription will be the store assigned to orders generated from installments from the subscription) products shipping methods shipping fees payment methods oms does not restrict products in one store from being added to an order in a different store for example, oms will allow a product assigned to the wholesale store to be added to an order assigned to the d2c store each store can be configured uniquely there is no shared or common configuration between multiple stores, however stores can be configured with the same settings use cases chord's multi store architecture within the oms allows for the support of a variety of different use cases examples store types chord's customers today can create two parallel stores each with their own store settings configurations each store can be pointed to a specific 3pl, it's own cms instance (for a custom product catalog) and be configured with a unique stripe account examples d2c, wholesale regional/country specific stores chord oms allows for the creation of country specific stores that can be used to in addition to language, the locale contains a country code; together the locale represents the identifier to be used to toggle in between different country based stores example a canadian store & a us store note support for locale specific stores requires that a store be configured per each locale this allows for seamless country toggling and proper cart management creating a new store new stores can be created in the store setup page of store settings to create a new store, click the "new store" button in the top right corner add the new store's site name , slug , site url and mail from address once configured, all stores will co exist on the store setup page specific store settings can be accessed via the the edit icon on the far right supporting multiple stores in the storefront directing api requests to different stores is controlled by setting the acs store header in the storefront code refer to store selection documents for more details most multi store customers implement a store selector control on their storefront to allow their customers to choose which store to shop from usually, this control is a dropdown in the header or footer when their customers choose a different value in that store selector storefronts using chord's client side sdks will want to change the storeslug and storeid given to the chordprovider this will provide the correct acs store header in all api requests made with the sdk storefronts interacting directly with chordoms' api will want to provide the store's slug to the acs store header in all api requests