Skip to main content

Understanding shop configurations

Shop configuration settings govern storefront behavior such as order approval, stock enforcement at checkout, and price rounding.

N
Written by Niyaz

Shop configuration settings govern storefront behavior such as order approval, stock enforcement at checkout, and price rounding.

How the page is organized

The Shop configuration page has these tabs, in order: Synchronization, Account, Catalog, Product Variants, Order, Shipping, Pricing, Promotions, Stock, Legacy Records, Logging, Usual Cart, Cart: Scanning And Upload, Cloudflare, Recommendations, Notifications, Storefront Forms, Document Lists.

  • The Synchronization tab offers ERP or System management for categories, currencies, packages, users, and customer roles.

Shop configuration page with its tabs and Synchronization management choices.

Cart scanning and spreadsheet uploads

Spreadsheet upload, automatic barcode scanner detection, and camera scanning are independently configurable and are all off by default. Enabling spreadsheet upload makes the cart upload feature available; scanner detection and camera scanning each enable their corresponding cart controls.

Code lookup requires a logged-in customer and at least one scanning feature enabled, and only returns products visible to that shopper. Spreadsheet imports provide a preview before committing, report rejected or adjusted rows, and use shop pricing rather than spreadsheet prices. Importing can add to the existing cart or replace its contents; minimum order checks remain at checkout.

Saving settings

The page has one toolbar with Cancel and Save. When the page opens, Save is unavailable. Saving an existing setting updates its stored value without creating a duplicate.

Creating or overwriting a setting through the shop configuration screen can raise a store setting changed event. An automation on this event can track setting changes; a condition on the setting name limits it to the setting you want to monitor. Without that condition, the automation runs whenever any setting is saved. The notification log leaves out the values themselves, since some settings hold secret information.

Why these settings matter

A few of these settings shape how orders behave, for example whether they wait for approval, whether checkout enforces stock, and how prices are rounded, and a wrong value may only show up when an order fails.

Who owns the data on the Synchronization tab

The tab has one choice for each of Categories, Currencies, Packages, Users, and Customer Roles. Each choice offers two options: ERP and System. The Synchronization guidance warns that switching to ERP mode loses settings made through System mode.

In System mode, the first synchronization can use the matching ERP Manager setting to sync once; in ERP mode, data comes from the ERP. For Customer Roles, ERP means Phonebook synchronization overwrites roles; System means manual management, with the admin interface described as a future feature.

What synchronization does not decide

Synchronizing product data by itself never makes DigiTrade the authority for that product data. The ERP or another owning system keeps the final say on accounting, issued invoices and other financial documents, tax results, reservations and how much stock is on hand. Do not treat a completed product synchronization as proof that DigiTrade now owns the synchronized product records.

Related

Did this answer your question?