Configuring stores

❗️

The decision to use stores must be done before setting up the production platform. Your solution consultant will discuss this with you. Stores condition the whole data integration process, and the decision to use them cannot be reversed.

Stores allow the management of several e-commerce websites using specific URLs, from the same back-office in DJUST. This is useful if you address several segments of one market, different audiences and/or geographical areas, but need to manage all your websites from the same DJUST account.

Stores allow doing plenty of customization, but they are complex and can involve a lot of set up work. DJUST recommends using stores only if you are sure this is the best feature to address your use case (to be discussed with your solution consultant). You can check other features (prices different for customers or customer groups, customization of navigation categories, interactive rules module...) that also allow for catalog customization.

⚠️

Stores are not meant to manage prices and catalog views, which is done with the interactive rules module. You can, if needed, use a combination of stores and catalog views to provide users with specific, dedicated product selections.

💡

As the back office for stores is not finalized yet, prefer using .csv files to handle the import and updates of stores data.

Store data model

Your data model is the same for all stores (if you have multiple stores), but you will be able to contextualize your catalog by store, by filtering some products that you do not want to appear in one store but in the others.

Parameters (front-office)

Each store can have its own offers, products, suppliers, navigation categories, users and emails. In the back office, the data model appears the same; filtering is done through each website.

DJUST handles the configuration (if we are in charge of the front office). If you are handling it yourself, the right store needs to be called through the API. Refer to our API reference documentation for more information.

Specific to stores
Suppliers are affected to stores through the .CSV import (or through Mirakl). This cannot be done through the back office yet.
Attributes can be assigned to one or multiple stores. Attributes properties are common between all stores.
Products are assigned per store. Their status (active / inactive) is however shared through all stores (one product cannot be active in one store and inactive in another one).
Offer stock status (active / inactive) is shared through all stores (one offer stock cannot be active in one store and inactive in another one).
Offer price is defined at the store level.
Stores architecture
Stores architecture

As indicated above, all stores share

  • Accounts
  • Attributes
  • Classifications
  • Custom fields and Tags

But have their own offers, suppliers, products, users and emails, as well as specific navigation categories for the different front offices.

Managing stores with multiple suppliers

Platform operators create supplier accounts. In the context of multiple stores and multiple suppliers, suppliers can be assigned to specific stores. Suppliers that are not assigned to a specific store will not be able to see it in their back-office and will not have access to the related data (sales, orders, products, etc.). One supplier can be assigned to one or several stores, and one store can host one or several suppliers. The operator remains in control of product approval for all stores. When customers order on a specific store, the order appears only on the back-office of this specific store.

⚠️

The catalog views (catalog filtering) are linked to the account, whereas the environment (products, offers) is linked to the store.

Create stores

  1. Click SettingsStores.
    Stores menu
  2. Click the + Add store button.
    Add stores
  3. Fill in the Name, Description and an external ID for your store.
  1. Click Create.

    The new store appears right away in the list. Its default status is "Active".

Create store views (optional)

Store views are optional. Unless you have very specific needs that cannot be fulfilled by other features (catalog views, prices per customers, dynamic rules, etc.), we do not recommend using store views for the moment. If in doubt, contact your solution consultant.

  1. Click an existing store, then + Add store view.

  2. Fill in a Name and an External ID for your store view.

  3. Click Create.

    The new store view is visible in the list right away. Its status will be "active" by default.

Import store data

If you choose to import store data through a .csv file, use the following templates to structure your files. Do not hesitate to ask your solution consultant for ready-to-use templates, to make sure you are always using the most up-to-date version.

Classifications

NameDescriptionMandatory (Y/N)TypeExample
nameProduct's nameYTextiPhone
external_idExternal reference (ID in the ERP)YText12345
descriptionProduct's descriptionNTextSmartphone made by Apple that combines a computer, iPod, digital camera and cellular phone into one device with a touchscreen interface.
brandProduct's brandNTextApple
productUnitProduct's base unitNItemItem
productParentIdTo input only in case of multiple variantsNNumber456789
classification_category_idClassification category IDYTextC1
gtinUPC (US) / EAN (Europe) / GTIN. Product's barcode classificationNText1234567890
mpnManufacturer Part Number - ID provided by the supplierNTextHSC0424PP
external_skuOption to add a second external reference for your system. Must be unique.NText
main_imageMain image URL.YText<https://www.apple.com/euro/iphone-15/a/generic/images/overview/closer-look/pink_small_2x.jpg>
additional_image_1Additional image URLNText
additional_image_2Additional image URLNText
additional_image_3Additional image URLNText
attributes_valueAdd custom attributesYATTR_externalidColumn name: attr_description. Value: description_name
deletePossibility to delete a productNIf set to TRUE, deletes to product.FALSE
StoreStore's external ID in which to send the productNIf empty, product is sent to all stores.32322||5243||6363

Attributes

NameDescriptionMandatory (Y/N)Type
nameAttribute's nameYText
external_idAttribute's external IDYNumber
typeAttribute's formatYTEXT, LONG_TEXT, COLOR, LIST_METRIC or LIST_TEXT or LIST_COLOR, DATE, METRIC, NUMBER
multiOffer multiple choices' selection for list-type attributesNTRUE / FALSE
unitTypeUnit for the unitType "metric"NWEIGHT_METRIC, VOLUME_METRIC, LENGTH_METRIC, AREA_METRIC, WEIGHT_IMPERIAL, VOLUME_IMPERIAL, LENGTH_IMPERIAL, AREA_IMPERIAL
unitUnit to provide for the "metric" typeNFor WEIGHT_METRIC: kg, g, mg. For VOLUME_METRIC: m3, L, cL, mL. For LENGTH_METRIC: m, cm. For AREA_METRIC: m2. For WEIGHT_IMPERIAL: lb, oz. For VOLUME_IMPERIAL: gal, qt, pt, fl oz. For LENGTH_IMPERIAL: yd, ft, in. For AREA_IMPERIAL: ft2.
attribute_valuesPossibility to add custom fields or attributesNvalue||value||value
StoreStore for which the attribute is availableYText or number

Offers

NameDescriptionCommentTypeExample
stock_idMANDATORY. Stock ID (can be the offer ID if no stock).external_idTextS_FRNS_PRODUCT
supplier_idMANDATORY. Supplier code (internal to DJUST)external_idTextFRNS_123
variant_idMANDATORY. Product's code or variant's code if anyexternal_idText1234G003
stockStock quantityIf there is no unit in the stock, the offer will not appear on the frontNumber10
deletedPossibility to delete an offer. If set to TRUE, deletes the offer.TRUE / FALSEFALSE
activeOffer status.TRUE / FALSETRUE
packing_typePackaging type: unit, box, bottle...TextUNIT
quantity_per_itemQuantity contained in a package (expressed in the product's base unit)Default: 1Number1
currencyOffer's currencyDefault: EURTextEUR
customFieldValuesCustom field for offersEach column associated with a custom field must be appended with CF_. Example: CF_WAREHOUSE. One column per custom field is required.TextColumn name: CF_WAREHOUSE, value: 1234
offer_idMANDATORY. External reference for the price offer, in case of several prices for a same stock.The external_id can be identical to the stock_id if only one priceTextO_FRNS_PRODUCT
offer_typePublic prices (for all customers) or private prices (specific to a customer)PUBLIC for public prices, ACCOUNT for specific pricesTextACCOUNT
account_external_idClient reference for a private priceexternal_idText1234
item_per_packNumber of product units in the offer packaging1 for unitary sale, 6 for a pack of 6 productsNumber1
min_order_quantityMinimum quantity for an orderDefault: 1Number1
price_rangeUnitary price for the productFormat is quantity|price|discount price. Use `` to indicate next range. If there is no discount price, only use quantity|price. If only price is input, we deduce a quantity of 1.TextSingle price: 2|5. Price range: 2|5||10|4
storeStore on which the offer is displayed1 line per storeNumber or text, depending on the store external IDRAO

Users

NameDescriptionMandatory (Y/N)TypePossible value
externalIdID user defined by clientYText
civilityUser's civilityYTextMR, MRS, MISS
firstNameUser's first nameYText
lastNameUser's last nameYText
emailUser emailYText
phoneUser's phone numberYNumber
groupsUser's role in the front-officeYTextFOC_Admin, FOC_User, FOC_Webmaster
organisationIdsOrganisation's external ID
mainOrganisationIdMain organisation's external ID
accountIdsUser's account external IDY
passwordUser's passwordN
inactiveActivate or deactivate the account. If set to TRUE, user is active.TRUE/FALSETRUE
deleteDelete or keep the user. If set to TRUE, user is deleted.NTRUE/FALSEFALSE
storeStore's external IDY