↑↓ selectEnter openEsc close

    1. Elbuz

    How to set up an Elbuz CMS store and its modules in the app

    5 min readUpdated

    Payments, delivery, SEO, integrations and other Elbuz CMS modules are set up in the “Store settings” window of the Elbuz app. After “Save”, changes go to the store at once.

    When you need it:

    • Connecting payments or delivery — the list shows missing keys.
    • Taking a module off the site — one switch in the list; keys and values stay.
    • Not sure changes got through — the “Not applied” tile and the module icon show the store has not accepted them.
    • A store module was updated — “Refresh from store” loads new fields; your values stay.

    Where to start: in “Store settings”, go through the modules with an exclamation mark.

    What the “Store settings” window does

    How to find a module and see what is wrong

    Until you have a store, the window shows “No store yet” and an “Open "Data export"” button.

    Modules are grouped into sections: “Store”, “Catalog”, “Checkout & payment”, “Delivery”, “Marketing & promotions”, “SEO & URLs”, “Integrations”, “Security”. The section buttons at the top scroll to the one you need. The “Search modules” box searches by module and section name.

    The tiles in the header count modules: total, enabled, not set up, not applied. Non-zero “Not set up” and “Not applied” are highlighted. Clicking a tile leaves only those modules in the list; “Modules” shows them all again.

    The Store settings window with the summary tiles, section buttons, module search and the Store section
    1Not set up
    2Not applied
    3Refresh from store
    4Search modules
    5Always on
    6Design editor
    1. Modules that lack required fields; a click leaves only them in the list.
    2. Modules whose latest values the store has not accepted yet.
    3. Re-reads the module list, field names and lists from the store; your values are not changed.
    4. Searches by module name and section name.
    5. The module is always on and can only be configured.
    6. Opens the design editor on the site in a new tab.

    Modules are shown as cards. The icon next to the name shows the module’s state. Hover over the icon to see a tooltip.

    • Green check mark — the module is set up and applied in the store.
    • Exclamation mark with “keys needed” or “empty fields: N” — the module will not work without these fields. The tooltip lists which ones.
    • Cloud with an arrow — saved in the app, not yet accepted by the store (why).

    Next to the module name there is a switch and a settings button. The switch turns the module on and off on the site. A lock instead of a switch means “Always on”: the store always needs this module, so you can only set it up.

    The settings button opens the module screen. Store pages, coupons and the chat assistant are managed in their own windows: a click opens them.

    Top of the Checkout & payment section with module cards and a tooltip listing the missing keys
    1Keys needed badge
    2Enable switch
    3Settings icon
    4Green check
    1. The module is missing keys; the tooltip lists which ones.
    2. Turns the module on in the store right away, but a module without keys will not switch on — its screen opens instead.
    3. Opens the module screen, same as clicking the card.
    4. The module is set up and applied in the store.

    The “Store theme” module also has a “Design editor” button. It opens the editor on the site in a new tab. The link is single-use and works for 10 minutes.

    How to turn a module on or off

    The switch in the list saves only “Enabled” and sends it to the store right away. It does not change the module’s other values: a disabled module disappears from the site, while its keys and settings stay in the app. Turn it on again, and the module works with the same values.

    A module with an exclamation mark cannot be turned on from the list: the app opens its screen so you can fill in what is missing.

    On the module screen, the “Enabled” switch sits in the header and takes effect only together with “Save”. System modules have no switch.

    How to set up a module and see what is missing

    Click the module card or the settings button next to its name. The screen opens in a separate window, with the module list still beside it. The “Still to set up” list on the right updates as you fill in fields: once nothing is missing, it shows “Everything is set up”.

    The monobank payments module screen with status, section buttons and the store status card
    1Module state
    2Enabled switch
    3Help
    4Section buttons
    5Still to set up
    6Changes in the store
    1. Module state: connected, not set up, disabled or apply error.
    2. Turns the module on at the site; takes effect together with Save.
    3. The article about the module opens at the side.
    4. Jumps to the settings blocks.
    5. What the module needs to work; a click leads to the field.
    6. Whether the store accepted the latest values.
    • Blocks by topic. The buttons at the top jump to blocks, and “Search settings” finds a field by name. Rarely used options are in the collapsed “Advanced” block. Fields that depend on a switch appear once you turn it on.
    • “Still to set up” — what the module cannot work without. Clicking an item takes you to the field. Items in grey are optional extras.
    • “Status in the store” — the “Changes in the store” line shows whether the latest values are applied. “Updated from the store” shows when the app last read the module description.
    • Tiles in the header — 30-day figures, if there is data. For payments: orders, total, average order value and the share of canceled and returned orders, with the “Payments, last 30 days” chart on the right. Delivery, reviews, questions, search and the Telegram store also have tiles.
    • Multilingual texts are filled in for each store language; the main language is expanded.

    The “Help” button in the header opens an article about the module in a side panel over the screen. If the store has related articles, they are at the bottom, under “Related articles”. If there is no button, the store has not sent help for this module.

    Help panel with the article about payments via monobank
    1Article title
    1. The module help comes from the store and opens over the settings screen.

    What happens after “Save”

    The “Save” button becomes active after the first change, and “Unsaved changes” appears at the bottom. The app first checks the fields, then saves the values on its side and sends the module to the store.

    • Empty field or wrong format — red text under the field and a “Not saved” message at the bottom. Nothing is saved, not even the correct fields.
    • The store accepted it — “Saved and applied in the store” with the save time. If the values did not change — “Saved, the store already has these values”.
    • The store rejected it — the app keeps the values; the rejection reason appears by the field. One rejected field stops the whole module: the store keeps the previous values.
    • The store did not respond — the app keeps the values, and they will reach the store on their own.
    Paysera screen: empty required fields in red and the Not saved message in the footer
    1Required-field message
    2Not saved message
    1. A required field is empty: the module will not work without it.
    2. Nothing is saved until the field is fixed.

    What “not applied” means

    The app has the values, but the store has not accepted them yet: it rejected them or did not respond. The app resends a module that did not get through with the next store export. There is no separate “send again” button.

    Resending will not fix rejected values. The app shows the reason for the rejection next to the field only right after “Save”.

    To see it again, open the module, change any field and change it back — “Save” becomes active — and save. Then fix the field with red text and save again.

    How to set, replace or clear a service key

    The app stores keys, tokens and passwords for payment and other services encrypted. Instead of the value, the screen says “set”: the value is not shown and is not read back from the store.

    The test password / secret key field of the monobank block in the saved state
    1set
    2Replace
    3Clear
    1. The key is stored encrypted; the value itself is never shown.
    2. Opens a field for a new key; it goes to the store after Save.
    3. Erases the key in the store too after Save.
    • “Replace” — a field for the new key appears. The new key goes to the store after “Save”.
    • “Clear” — after you confirm, the key is erased on save, in the store too. The only way to get it back is to enter it again.
    • “Cancel” — keep the key as it was.

    An empty key field does not change the store. So a key that was already in the store keeps working and is shown as “set”.

    When to click “Refresh from store”

    The app takes the module description from the store and remembers it. The date in the window header, “Store data as of …”, shows when it was read.

    “Refresh from store” rereads the module list, field labels and store lists: order statuses, zones, customer groups. Your values are not changed.

    Click it when:

    • a new module or a new module field is missing from the list;
    • a drop-down is empty and the hint asks you to refresh the data;
    • a field asks you to refresh data from the store.

    For a module the app has not seen before, it copies the current values from the store, except keys.

    What Elbuz sets up for you

    Service modules are not in the list: photos in cloud storage, store email, page cache, language editor, fast photo display and store analytics. Elbuz sets them up when the store is created, and they work without your involvement. The store clears its page cache on its own after every accepted settings change.

    Scenarios

    Connect a new payment method

    In “Checkout & payment”, open the payment method with an exclamation mark → paste the keys from the payment service dashboard → turn on “Enabled” in the header → “Save”. It is done when “Saved and applied in the store” appears at the bottom and the module has a check mark in the list.

    Take a module off the site for a while

    Turn off the module’s switch in the list. Customers no longer see it; its keys and settings are kept. To bring it back, use the same switch.

    Replace a service key

    Open the module, click “Replace” next to the key, paste the new one and save. The new key replaces the old one in the store.

    The “Not applied” tile is above zero

    Click the tile — the list keeps only those modules. If the site was not responding, the values will get through with the next export. If the store rejected them, save the module again as described in “not applied” and fix the field it marks.

    What to do when changes did not get through

    App messages
    What you seeWhyWhat to do
    “Fill in the required module fields first, then enable it” A module without required fields was turned on with the switch in the list Fill in the “Still to set up” items on the module screen and turn it on there
    “The store did not accept the change” The switch in the list did not reach the store Open the module and turn it on there — the reason will appear next to the field
    “Not saved: fix the fields marked in red” Empty field or a value in the wrong format Fix the field with red text and click “Save”
    “First set up and turn on “Form protection (reCAPTCHA)”” reCAPTCHA is selected in “Store options”, but its module has no keys Click “Open the module” under the field, save the keys, then the options
    “Not saved: no connection to the server” The app got no response to the save Check your internet connection and click “Save” again
    “The store did not accept some values: see the highlighted fields” The store rejected values, and the module kept the previous ones Fix the highlighted fields and save
    “The store did not accept the settings” The store did not respond or rejected the module without pointing to a field Check that the site opens. If it was not responding, the values will go through with the next export; if it opens, contact support
    “The store does not know this field. Refresh data from the store” The module was updated in the store, and the app remembers the old description “Refresh from store”, then save again
    “The store reference list is empty. Press "Refresh from store" in the settings window” A store list (statuses, zones) has not been read yet “Refresh from store” in the “Store settings” window
    “Not in the store catalog: upload it to the store or choose another one” The selected product, category or brand has not been exported to the site yet Export the item to the site or pick a different one
    “Key not saved: encryption is not set up on the server. Contact Elbuz support” The key cannot be saved encrypted Contact Elbuz support
    “Could not read store settings” The store did not respond when the window was opened Check that the site opens and click “Try again”

    FAQ

    I saved, but the site still shows the old version. Why?

    Values apply right away, and the store clears its page cache itself. Some module work runs in the background within 5 minutes, such as rebuilding page addresses or connecting the Telegram bot. If the module in the list shows the “not applied in the store yet” icon, see this section.

    Why is “Not set up” above zero when these modules are turned off?

    The tile counts modules that lack required fields, regardless of the switch. A disabled module without keys does not affect the site.

    Where do I change the store name, contacts and company details?

    In your company card in Elbuz, not in this window. The store gets them after you save the card. More: what data the store takes from Elbuz.

    Why is the module I need not in the list?

    Elbuz manages service modules itself (list). Modules with nothing to set up, such as “Product filter”, are not shown either. A module that appeared in the store recently will show up after “Refresh from store”.

    How do I open the general store options directly?

    In the “Elbuz CMS” template → “Store management” → “Store options”. In the “Store settings” window, they come first in the “Store” section.

    Where to find it and who has access

    Menu
    Directories → Operations → Store settings
    Other entry points
    the “Elbuz CMS” template → “Store management” → “Settings and modules”
    Access rights
    the “Store settings” window in group permissions; pages and coupons — the permissions of their windows
    Prepare
    a created Elbuz CMS store, keys from the service dashboards

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free