Marketplace Card
The Marketplace Card shows details of an individual marketplace registration and provides navigation to the marketplace-specific dashboard and setup.
Opening the Page
- Click an entry in the Marketplace List.
Fields
| Field | Description |
|---|---|
| Code | Unique marketplace code. |
| Name | Display name. |
| Active | Activation status. |
| Connector App | Name of the installed connector app. |
| Last Synchronization | Timestamp of the last successful synchronization. |
| Last Error | The last error that concerns the marketplace as a whole – such as authentication, connection or setup – with its time; the Status is then Error. Problems of a single order, such as an order held for an unknown item, are shown on the order and in the Activity Log, not here. Clear Error empties the error and resets the status. |
Prices
The prices of a marketplace come from one sales price list per sales channel. The Price Engine writes one such list per sales channel, but any Business Central sales price list will do. There is no fallback to the unit price on the item card: an item without a price in its list gets a price error, and no price is sent for it.
These sections appear only for marketplaces whose connector takes its prices from the sales price lists.
- Marketplace with sales channels (e.g. Kaufland per country, Shopware per shop): assign each channel its price list in the Sales Channels section.
- Marketplace without sales channels (e.g. Otto): assign the price list to the marketplace itself in the Prices section.
| Field | Description |
|---|---|
| Price List Code | Sales price list the prices come from. |
| Sales Currency | Currency the marketplace sells in on this channel (reported by the connector). |
| Currency Code | Currency of the price list. Prices are sent in this currency; it must match the sales currency, otherwise the channel gets an error and no item gets a price. merchantCENTRAL does not convert. Empty means the local currency. |
| Prices Including VAT | Whether the prices in the list include VAT. Where needed, the connector converts with the VAT rate from the price list's VAT business posting group and the item's VAT product posting group. |
| Items with Price Error | Items without a valid price. Click to see them with the reason. |
Which price applies
- Only active lines of an active list that are valid today.
- Only lines for a quantity of one – tier prices do not count as the item price. Connectors that send tiers (Shopware 6) get the lines for larger quantities by the same rules; for a bundle counted in whole bundles.
- A line for a variant applies to that variant, a line without a variant to all of them.
- Lines in the base unit come first. If there is only a line in the sales unit, it is converted to the base unit.
- If several lines apply, the lowest price wins. A promotion with an end date therefore applies while it runs, and the regular price after that.
Before every price sync, merchantCENTRAL takes the prices from the lists. Only changed prices are sent. A tier that is added, changed or removed counts as a change as well, even when the price stays the same. An item with Price Fixed keeps the price entered by hand. If an item is a bundle, the price per piece is multiplied by the Bundle Content.
Business price
Some marketplaces offer business customers a price of their own for the same offer (Amazon Business). For them, each sales channel has a Business Price List Code on its card as well. The Price Engine writes a second list per channel for it, told apart by the customer price group.
- The business price list must have the same currency and the same VAT basis (including or excluding VAT) as the price list of the channel, because both prices are sent together. If they differ, the channel gets a price error.
- The business price follows the same rules as the price (see above). An item without a line in the business price list has no business price – that is no error, not every item is offered to business customers.
- Quantity tiers for business customers come from the business price list.
- The price and the business price are taken, checked and sent together: if the price check blocks one of them, the other waits too.
- Items for business customers only (e.g. Amazon "B2B only"): if an item has no price in the price list but a business price, the connector can declare the price not needed. The item is then sent with its business price alone; the Price is 0, there is no price error, and the price check judges only the business price. If the business price is missing as well, the price error stays.
The field only appears for marketplaces whose connector sends business prices.
Price Check
A price that reaches the marketplace is an offer customers buy at. The Price Plausibility Check holds back an obviously wrong price before it is sent: the item gets the reason as its price error, and the marketplace keeps its current price. The blocked price does not replace the price of the item but waits beside it as Blocked Price. The other items carry on.
| Field | Description |
|---|---|
| Price Plausibility Check | Switches the check on. Off by default – an update never starts blocking prices on its own. |
| Block Price Below Unit Cost | Blocks a net price below the unit cost of the item. Preset. |
| Min. Margin % | Smallest margin: (net price − unit cost) / net price. 0 switches the rule off. |
| Max. Deviation from Last Price % | How far a new price may fall below the price the marketplace last accepted. A price increase is not held back by this limit – the marketplace would otherwise go on selling at the old, lower price. A decimal slip – more than three times or less than a third of the last price – is always held back, whatever the limit. Preset to 30. 0 switches the limit off. |
| Blocked Prices | How many prices are blocked right now. Click to open the Blocked Prices. |
The rules are checked in this order, and the first one that applies counts. Everything is measured net and in the currency of the price list. Unit cost and margin apply to the lowest amount that is sent – the price, or a lower tier, because in B2B the tier is the price that gets ordered. Every price sync checks these two rules for unchanged prices as well: a tier or the unit cost can change while the price stays. The unit cost is converted with today's exchange rate for this and multiplied by the bundle content; the price that is sent is never converted. Items without a unit cost and currencies without an exchange rate are not affected by the cost rules, items without an accepted price not by the deviation.
Each sales channel can override the settings on its card: Default takes the setting of the marketplace, Yes or No applies to the channel only. A blank limit takes the one of the marketplace; to run a channel without a limit, set its check to No.
A fixed price is checked when it is entered: if it breaks a rule, merchantCENTRAL asks. Confirming counts as the approval, and the price is sent.
A business price is checked by the same rules, measured against its own last published business price. The price error then starts with "Business price:".
Handling Time
A marketplace promises your customers a handling time and counts every late shipment against your account – Amazon suspends from a late shipment rate of 4 %. With Use Handling Time, merchantCENTRAL only reports stock that can be shipped within the promise.
| Field | Description |
|---|---|
| Use Handling Time | Switches the rule on. Off by default – running channels do not change with an update. When off, all sources of stock count as before, and the promise is the handling time of the slowest contributing source. |
| Max. Handling Time (Days) | Longest promise in working days. Sources that need longer do not count towards the quantity. Empty = no maximum. |
| Min. Quantity for Promise | How many units the fastest sources must hold together before their handling time is promised. Set to 1 when you switch the rule on. |
When on, your own stock and the vendors are taken from the fastest to the slowest source until the minimum quantity is reached. The quantity of all sources up to that handling time is reported. Safety stock, bundle, percentage and maximum quantity apply afterwards as usual.
Each sales channel can override these settings on its card: Default takes the setting of the marketplace, Yes or No applies to the channel only, and an empty value takes the one of the marketplace.
→ Rule, example and master data: Handling Time.
Cancellations
When a position is cancelled on the marketplace after its sales order was created, merchantCENTRAL takes it out of the sales order – as long as nothing has been picked, shipped or invoiced.
| Field | Description |
|---|---|
| Cancellation Handling | Automatic (default) changes the sales order as soon as the cancellation arrives. Manual keeps the cancellation on the Order Cancellations page until you apply it. |
→ Process and special cases: Order Cancellations.
Order Automation
The job queue can release and post imported orders shortly after the import. How far this goes you set separately: for orders you ship yourself and for orders the marketplace ships from its own warehouse (such as Amazon FBA). The connector reports which kind an order is when it imports it.
| Field | Description |
|---|---|
| Order Automation | For orders you ship yourself. |
| Automation for Orders Shipped by Marketplace | For orders the marketplace ships. Such an order has been shipped already, so Release and Post Shipment and Invoice is common. Make sure the order has the location of the marketplace warehouse – otherwise posting the shipment takes the stock from your own warehouse. |
Both fields have the same values: None (default, the order stays open), Release, Release and Post Shipment and Release and Post Shipment and Invoice. The import queues the sales order; a job queue entry processes the queue every 5 minutes, each order on its own. merchantCENTRAL creates the job as soon as you set a field to a value other than None. Orders that could not be released or posted are listed with the error on the Order Automation Entries page and on the hub dashboard.
Settlements
The accounts the settlements of this marketplace are posted through. Journal, clearing account and tolerance apply to all marketplaces and are set on the merchantCENTRAL Setup.
| Field | Description |
|---|---|
| Settlement Bank Account | G/L account the payouts are posted to. |
| Settlement Transit Account | G/L account that holds the money between the sale and the payout; every settlement line is posted against it, so a fully explained payout leaves it at zero. |
Actions
| Action | Description |
|---|---|
| Open Dashboard | Navigates to the marketplace-specific dashboard (e.g., Amazon Dashboard). |
| Open Setup | Navigates to the marketplace-specific setup. |
| Import Orders | After a confirmation, imports the new orders of the marketplace; the message names the number of imported orders. |
| Sync Prices | Takes the prices from the price lists and sends the changed ones to the marketplace. |
| Calculate Prices | Takes the prices from the price lists without sending anything, and shows how many changed, how many items have no price and how many prices the price check blocks. Use it to check the price lists before the first sync. |
| Data Takeover | Opens the Data Takeover, filtered to this marketplace. |
| Settlement Account Mapping | Opens the Settlement Account Mapping, filtered to this marketplace. |
| Settlements | Opens the settlements of this marketplace, to match and post them. |
| Migrate Historical Orders | After a confirmation, takes the order history of the marketplace over into the central marketplace orders, for the revenue statistics – a one-time step when switching over. The connector decides what is taken over. The marketplace must be enabled and licensed. The message names the number of orders taken over. For Amazon, see below. |
Historical orders for Amazon
For the marketplace AMAZON, Migrate Historical Orders runs step 7 Order History of the Amazon data takeover, for all marketplaces whose applied cut-over date has begun. The connector shows a message of its own per marketplace only when a marketplace stopped or failed. If no marketplace has a cut-over date, the action ends with the error No marketplace for this step; likewise if no applied cut-over date has begun. The message leads to Marketplaces and Cut-over Dates. The same step also runs in the Data Takeover.
Tooltip of the action
The tooltip still speaks of a takeover from the connector-specific tables. For Amazon, the action reads the orders at Amazon itself (report of all orders), not from tables in Business Central.
Attributes
| Action | Description |
|---|---|
| Attribute Mappings | Opens the Attribute Mappings of the marketplace. |
| Category Mapping | Opens the Category Mapping of the marketplace. |
| Attribute Issues | Opens the Attribute Issues of the marketplace's listings. |