Tutorial: Shop Dashboard

The shop dashboard is the central work overview for the ongoing shop operation. It shows open work, warns of scarce stock and leads directly to products, orders, groups, channels, media, legal texts and revocations. This tutorial explains all areas and the associated possibilities step by step.

Open shop dashboard

Open shop dashboard and use it correctly

1. Sign up with a user who is allowed to use the shop administration.
2. Open in the top menu Shop > Shop Dashboard.
3. Read the six key figures first. They show where work is currently waiting.
4. Then open the appropriate tile. Each tile leads to its own workspace.
5. The global Settlements Reach them through Shop > Settlements. They do not have their own dashboard tile, but they act on almost all other areas.

The six key figures explained exactly

1. Products – searching for, testing and processing assortment

Product management is the starting point for item master data, prices, availability, groups, attributes, images and sales channels.

Service the product list

1. Provide them with No. page the desired number of lines.
2. Choose one of them Sorting And the direction. For controls, item number, title, price and active status are particularly helpful.
3. In the search field, enter SKU, Title, Description, Group or Channel and click Apply.
4. In the columns Image, Item Groups, Attributes, Shipping Groups, Channel Groups, Channels, Price, VAT, Shipping and Status, check for completeness.
5. Open an article about Processing or his shop view of Views.

Completely create new articles

• Basic data: Unique item number/SCU, URL name, title, category, product type, active status and sorting.
• Description: Short description for maps and full text for detail page and export.
• Price and tax: Gross price and normally VAT inheritance from the primary product group.
• Dispatch: take shipping group or set individual shipping values only in a real special case.
• Stock: Maintain storage value when global inventory management is active.
• Presentation: Set badge, icon and optional logo variant.
• Images: Assign CMS media and choose exactly one meaningful primary image.
• Channels: Check direct channel allocation, inherited channel group and mapping separately.

Further product actions

• The Article group tree shows the group structure and supports the assignment.
• Article attributes opens the values of the characteristics defined for the product group.
• Channel mapping manages channel SKU, different price or shipping, category, external IDs and platform-specific mandatory fields.
• Multiple actions can assign tagged articles to groups or channels, remove assignments or trigger an export.
• Deletion moves an article to the trash after confirmation. Check open orders and external listings beforehand.

2. Orders – Control payment, processing and shipping

The order list contains orders from your own shop and from connected channels. The stored positions, prices, tax and legal texts are snapshots of the time of purchase and are not recalculated from later changed products.

Finding orders

1. Search by order number, customer, email, channel or payment reference.
2. Sort for day operation descending by date.
3. If necessary, filter by order, payment, shipping status or source channel.
4. Read the three status types separately: Order, Payment and Dispatch can have different stands.
5. Open the record about the editing action.

Process order in detail

• Quick actions: paid, processed, ready to be shipped, shipped, delivered/completed, cancelled or refunded.
• Payment status and reference: Change only based on a reliable provider response, bank booking or channel feedback.
• Invoice: Check the invoice number and date; Preview or create PDF and control the archived file path.
• Dispatch: Maintain status, service provider, tracking number, tracking URL and shipping time. For known service providers, a tracking URL can be supplemented during storage.
• Customer mail: Save first, then send the currently stored status. Prerequisite is a valid mail sender.
• Admin note: Document questions, special agreements or channel problems internally.
• History: Retrace status, payment, shipping, billing and cancellation events.
• Payload: use technical provider or channel raw data only for diagnosis; they may contain confidential information.

3. Product groups – define common product logic

Product groups structure the catalogue and provide reusable default values. An article should choose the appropriate group instead of duplicating control, display and gallery settings individually over and over again.

• Key: stable technical keys; do not change after creation without a migration plan.
• Upper group: Creates a hierarchy. Without an upper group, the group appears as the top catalogue group.
• Group and description: visible name and internal technical declaration.
• VAT category: refers to: mwst1, mwst2 or mwst3; the percentage comes from the shop settings.
• Group image: Image of the group tile and possible fallback. A new selection replaces the assignment, not the CMS file.
• Map and detail: Select the presentation in lists and on the product detail page.
• Gallery: Template, visible image number, fitting, lightbox width, overflow and click behavior.
• Article attributes: technical advice on the characteristics required for this group.
• Channel specifications: Standard categories or product types that can be overwritten in article mapping.
• Variety and active: Order and usability of the group.

Recommended procedure: Create group, set control class and presentation, select group image, define attributes and only then assign articles.

4. Attributes – Define group-specific characteristics

Attributes create structured input fields for products of a group, such as color, size, material, length, performance or runtime.

1. Choose the Product group, to which the attribute applies.
2. Forgive a short stable Key how farbe or leistung.
3. Wear the visible Title one.
4. Select the type Text, Number or Selection list.
5. Complete one unit for numbers; For selection lists, options with | separately.
6. Mark the attribute as Obligation, Filters or Comparison.
7. Set sorting and active status and save.
8. Then open the article attributes for the product and maintain the specific value.

5. Shipping groups – bundle delivery type, time and costs

Shipping groups separate digital delivery, services and physical delivery. Items can inherit the group completely or use their own shipping values in justified cases.

• Key: technical keys such as digital-free or merch-package.
• Group of dispatch: A visible name in product forms.
• Dispatch route: for example download, date, DHL package or forwarding.
• Time of delivery: understandable customer text such as “2-4 working days”.
• Gross costs: standard costs; 0 means free of charge.
• Free from gross: value of goods for free shipping; -1 does not mean an exemption.
• Variety and active: Order and usability.

For changes, check at least one digital, one physical and, if available, one service item in the shopping cart. This way you can detect faulty inheritance or double shipping costs.

6. Channel groups – assign sales channels as a set

Channel groups bundle multiple sales channels into one sales scenario. For example, an article can only be stored in the shop, in shop and Amazon or on several marketplaces.

1. Set a stable key and understandable name.
2. Describe which items belong to this sales scenario.
3. Only mark the channels that should actually be used for these articles.
4. Set sorting and active status and save.
5. Then assign the channel group to a product.
6. In the product, check whether a direct channel assignment overwrites the inherited group.

7. Channels – Configure shop and external platforms

A channel describes a single sales channel and its technical connection. The internal shop does not require an external API; Amazon, eBay and mobile.de may require API data. Classified ads should be operated manually without a shared interface.

Reading the channel list

• Platform: Shop, Amazon, eBay, classified ads, mobile.de or own channel.
• Connection: internal, manual, API, feed or webhook.
• Active: General release.
• Export: Articles may be prepared or transmitted for the channel.
• Order import: Orders or feedback may be accepted.
• Test status: the result of the last connection test; “Not tested” is not a successful connection.

Editing and testing channels

1. Check key, visible name, platform and connection mode.
2. Activate export and order import only for actually set up processes.
3. Enter API base URL, client ID, secret, tokens or user/password to match the provider.
4. Add Marketplace, Seller, Account, Location and Category Identifiers.
5. eBay requires additional payment, fulfillment and return policy IDs.
6. Feedback may require notification target, topic, roles/scopes, and webhook secret.
7. Save them and guide them. Test Off. The test checks mandatory fields and – if configured – a reading API access.
8. Only then assign the channel to a channel group or a single product.

8. Shop Media – assigning CMS files to articles and groups

Shop media is not a second file management. The files remain in the CMS media browser; dbxShop stores the use on the article or on the product group.

1. Choose an individual Article 1, one Product group or the desired combination.
2. Click on Load selection, to see the existing assignments for this context.
3. Wear them. Sorting for newly assigned images.
4. Activate them Primary imageif the new image is to appear as the main image.
5. Open over Selection the CMS media browser. Upload, trimming, size change, batch and maintenance are available there.
6. Then check image, alternative text, assignment target and order in Associated shop images.
7. Check the product card and product detail page in the frontend.

Remove an assignment: The trash on the shop image cancels the shop use. The CMS media file is preserved and can still be used elsewhere.

9. Legal texts – review and publish CMS content

The legal texts are used as a normal CMS page under shop-rechtstexte maintained. The shop admin shows CMS-ID, Permalink, Status, Reading Rights and Template as well as a preview.

1. Check if status Active and reading rights * Suitable for public shop use.
2. Click on Processingto open the CMS page.
3. Replace all sample and placeholder information with real operator, register, tax, payment and shipping data.
4. Save and control the first CMS view.
5. Then open them. Shop view and check presentation, links and accessibility without admin rights.
6. Run a test order and, if snapshots are activated, check whether the text valid at the time of purchase has been saved on the order.

10. Cancellations – Control request, inventory and refund

The area shows received revocations and returns with order number, customer, message, status and quick actions.

Via the bar actions you can edit the revocation text in the CMS and view the customer page in the shop. Reconcile order status, payment status, stock booking and actual repayment; a status alone does not demonstrably perform an external provider refund.

11. Settings – Setting global shop rules

The settings act as a common basis for articles, groups, checkout, payments, shipping, emails, channels and media. Changes can therefore immediately affect several areas.

Global shop counters

• Shop active: General release of the shop functions.
• B2B mode: Preparation for business, net and other B2B rules.
• Use stock: activates stock logic and the indicator "Low stock".
• Using Channels: enables external channel functions; for pure shop installations, the switch can remain off.
• Guest order: Allows checkout without an existing account.
• Legal text snapshot: saves the texts used at the time of purchase to the order.
• Show revocation: Displays the revocation area in the frontend.
• Customer and admin mail: control order and revocation notifications.

Currency, price and VAT

• Standard channel: Normally shop for internal shop orders.
• Standard currency: three-digit ISO code, such as: EUR.
• Price display: Gross for typical consumer shops, net only with suitable B2B and legal text logic.
• Standard VAT class: Fallback for new groups or ambiguous assignments.
• VAT notification: visible control indication; internal calculation and legal mandatory texts remain to be checked separately.
• mwst1 to mwst3: central name and percentage. Product groups select only the class; This causes a change to all inherited articles.

Payment, mail, shipping and media

• Advance payment: Fully maintain account holder, IBAN, BIC, bank and money order.
• Invoice: Activate only for suitable customer and approval processes.
• PayPal: First, enter and test Sandbox, Brand Name, Client ID and Secret.
• Amazon Pay: Sandbox/Live, Region, Merchant ID, Store ID, Public Key ID and Private Key Configure to match the environment.
• Test Payment: Check PayPal via OAuth and Amazon Pay access data as well as local signature. A technical test does not replace a complete test order.
• Mail sender/admin email: must fit the system mail configuration and your own domain.
• Digital downloads: activate only together with suitable product and withdrawal logic.
• Package shipping: global fallback if no more accurate shipping group applies.
• CMS Media slot: Normally shopChange only with a conscious migration plan.

Certainly change

1. Document the current status and determine the affected function.
2. Change and save only related fields.
3. Reopen the appropriate admin mask and check the stored values.
4. Check product card, detail page, shopping cart and checkout with a test item.
5. For payment or channel changes, remain in Sandbox or test environment until the complete process is successful.

Recommended Daily Shop Routine

1. Open dashboard and read open orders, payments, shipping and revocations.
2. Check orders descending by date and open new processes.
3. Match payment status with bank, provider or channel.
4. Process ready-to-ship operations and store tracking data.
5. Revocations are processed in due time.
6. In the case of active stock management, consider low stock items.
7. After changes, check an affected product page in the frontend.

Recommended setup procedure for a new shop

1. Settings: Set shop status, currency, price/tax display, checkout, mails, payments and shipping.
2. Groups of dispatch: Separate digital, physical and service channels.
3. Product groups: Define structure, VAT class, presentation and gallery.
4. Attributes: Create required characteristics per product group.
5. Channels: Configure and test internal shop and optional external platforms.
6. Channel groups: Create meaningful sales scenarios.
7. Products: Maintain master data, price, group, shipping, attributes, images and channel mapping.
8. Legal texts: Replace placeholders, check and check in the shop.
9. Test order: Catalogue, product detail, shopping cart, checkout, payment, mail, admin processing and revocation completely passed.
10. Release: only activate productive provider data or live operation after successful testing.

Targeting typical problems

Shop fully administeredUse the shop in the frontendAll tutorials