Lazada Philippines’ major promotion registration has just been approved, and prices are locked during the campaign period; on the same day, the same product on the Malaysia site should naturally be cheaper by a margin because taxes and last-mile shipping fees are lower. Operations is under pressure from two things at once: the campaign side requires no price changes, while buyers are using cross-site screenshots to demand a refund of the price difference. Most multi-site pricing problems are not about “not being unified,” but about unifying at the wrong layer—rules that should be unified were not set, while pricing that should not be leveled was leveled.
The problem encountered in Lazada multi-store management is the same problem in AliExpress multi-store management, Shopee multi-store management, and Mercado Libre multi-store management: limit unification to the three layers of rules, calendars, and approvals, and keep the three layers of pricing, inventory, and account environments isolated.
First distinguish which layer must be unified and which layer must be isolated
Three things must be unified:Rules for calculating costs and price gaps(which cost items are allowed into the price gap, and where the gross margin floor is),Promotion overlap windows(the four time points: registration deadline, campaign period, inventory lock, and lifting of the price-adjustment freeze),Price-change approval(who can submit, who reviews, and what records are kept).
The same three things must be isolated: each site's pricing calculation sheet, the inventory quota occupied by each site's promotions, and the account login environment. Dashboards can consolidate data, but account environments cannot—this point is covered inE-commerce multi-account management: key points for setting up login environments, sub-accounts, and operation logswhere it has already been broken down to the field level.
Doing the two sets of layers in reverse is the most common incident: rules are not set, yet prices are flattened first; data is not consolidated, yet accounts are merged onto one machine first.
Allowed price differences: on what basis is the benchmark price set for the same item across different sites
The benchmark price of the same item across different sites is not the same number; rather, it is the same set of breakdown criteria: procurement and first-leg shipping + site taxes and compliance + platform commission − platform subsidies + last-mile shipping + target gross margin, and finally it is calibrated once against the local competitor price band. If the price difference can be explained item by item by these factors, it is pricing; if it cannot be explained, then it is a conflict.
| Variable | Impact on price difference | Implementation approach |
|---|---|---|
| Exchange rates and collection costs | Local-currency settlement and differences in collection cycles determine the gross margin you can afford | Maintain the costing sheet in each site's local currency; do not convert RMB prices directly into each site's selling price |
| VAT and import duties | Taxes and duties are included in costs in different ways, so the cost base for the same product differs | Keep taxes and duties on a separate line; do not allocate them into the purchase price |
| Platform commissions and subsidies | What drives the most is the net price, not the list price | Record the list price and the net price in two separate columns: price-change approvals look at the list price, while conflict assessment looks at the net price |
| Last-mile shipping costs and fulfillment models | The per-order cost differs significantly across self-fulfillment, platform warehouses, and cross-border direct shipping | Build rows for shipping costs by "site + fulfillment method"; do not use averages |
| Competitor price bands and site sensitivity | The same price band corresponds to different purchasing power across sites | Maintain a price band upper limit per site; any price difference exceeding the upper limit is directly judged as a conflict |
| Channel model differences | Channels like Wayfair quote according to a wholesale/retail structure, with the baseline being B-side discount logic; Mercado Libre's installment and logistics policies rewrite buyers' actual spend | Channel models are assigned to a separate layer and are not placed into the same table for comparison with the retail prices of Lazada and Shopee |
Don't use a rule-of-thumb threshold like "the price gap must not exceed a certain percentage"—it cannot explain why the price gap exists, and it gives you no justification when your supervisor reviews it. For details on multi-currency accounting and timing coordination, refer toMulti-currency, multi-time zone, and logistics coordination: How to manage multiple stores in cross-border e-commerce.
Promo cadence alignment: Look at overlapping windows, not a unified calendar
Consolidating each site's promo calendar into one looks neat, but it actually creates two types of conflict: inventory that would not otherwise conflict gets locked up at the same time by activities in the same week; and because each site's registration deadline is different to begin with, a unified calendar is bound to miss the real deadline for a given site. The right approach is to plot each site's registration deadline, campaign start, inventory lock, and release from price-change freeze on the same axis, and look only at whether they overlap.
- Philippines site peak W3–W4
- Malaysia site peak W5–W6
- Thailand site peak W7–W8
The rule can be very short: reconcile the site calendars once every two weeks and mark the overlapping campaign windows within the next 8 weeks; within an overlapping window, sites that involve shared inventory do not make price adjustments without approval. An interval like W4–W6 in the chart, where all three sites overlap, is the segment where inventory allocation needs to be decided in advance—not something to argue about after registration.
Handling order for four types of price conflicts
Conflicts are not handled by who reports first; they are ordered by degree of irreversibility. A wrong price can be changed back; being ruled non-compliant by the platform, inventory being oversold, and shipping timeout are three things that are basically irreversible.
- Overlap between platform campaign prices and regular prices.Signal: a price-change request is received within the price-lock period, or the backend indicates that the price does not comply with campaign rules. The first step is not to change the price but to verify the campaign ID, effective time, and price-lock scope, and determine whether the target price falls within the freeze period—if it does, defer it until the campaign ends; if it does not, proceed to approval.
- Shared inventory is fought over by promotions across multiple stores.Signal: the two sites' campaigns fall in the same week, and sellable inventory is lower than the sum of the two sites' pre-locked quantities. The first step is to allocate inventory quota by campaign tier and record it in the campaign notes—lock quantity first, then release it.
- Price gap between stores for the same item exceeds the threshold.Signal: the price comparison table shows a price gap that cannot be explained by cost items, or customer service receives a cross-site price comparison complaint. The first step is to go back to the baseline price table and check item by item to find the missing cost line, rather than directly lowering the price at that site.
- False conflicts caused by platform subsidies and shipping estimates.Signal: the listed prices are the same but the final prices differ greatly, or the settlement amount is noticeably different from the estimate. The first step is to unify the final-price basis (including subsidies, shipping fees, and installments); most 'conflicts' disappear at this step.
Price-change permissions and audit trail: who can change prices at which layer
Price changes are divided into three stages: Operations submits a site price change, touching only the current site's price within the accounting basis; the supervisor reviews cross-store price gaps to determine whether the threshold is breached and whether it falls within an overlapping window; Finance reviews the exchange rate and subsidy basis to confirm that the cost items and final-price algorithm have not changed. The three stages have different change scopes, and when combined, the situation arises where 'Operations casually changes another site's price too.'
A price change record must include at least: site, original price and target price, effective time, associated campaign ID, occupied inventory lock quantity, submitter, and reviewer. These fields are the complete basis for after-the-fact review; if even one is missing, there is no way to explain why that was the price at the time.
If you are still relying on manual repeated logins and switching between each site's backend to change prices, first calculate the switching overhead clearly before deciding whether to adopt a tool; for the criteria, seeHow to operate multiple stores simultaneously? First investigate the losses caused by repeated logins and manual switching. A dashboard can unify this—combining multi-site prices, inventory, and campaign windows into a single view; this belongs toHow to unify management across multi-platform stores by centralizing orders, inventory, and messagesthe business process consolidation layer; account credentials, proxy egress, and browser environments belong to the asset layer and should remain isolated. When the team reaches 4 or more people, price change approval also needs role division; for reference, seeHow does one team manage multiple stores: role division, approval flow, and handover checklist.
Teams doing AliExpress store operations, Shopee store operations, or Mercado Libre store operations can directly reuse this sequence: unify rules and overlapping windows, isolate site pricing and account environments, and handle conflicts by degree of irreversibility. The difference lies in channel models—Wayfair seller operations are closer to wholesale quote logic, and Mercado Libre store operations' installment and logistics policies will alter buyers' actual spending; the landed price criteria for these two channel types must be managed in separate tables from the retail prices of Lazada and Shopee.
Frequently Asked Questions
Should the same item be priced exactly the same across multiple Lazada stores?
No, it doesn't need to be, and it shouldn't be. What needs to be consistent is the cost and price-difference rules, how overlapping windows are handled, and the price-change approval process; selling prices are calculated separately for each site based on taxes, shipping fees, commissions, and subsidies. If the price difference can be explained item by item by cost factors, it is intentional pricing.
When promotion periods overlap across different sites, which store should be paused first?
Look at the degree of irreversibility first, not sales. Do not stop sites that have entered the price-lock period, have locked inventory, or have already been approved for registration; stagger sites that are still in the registration window. When both sites have locked volumes but shared inventory is insufficient, split the pre-locked volumes according to campaign tier and notify the warehouse immediately.
Will using ERP for unified price changes increase the risk of account association?
Association determinations are usually the result of multiple layers of signals—credentials, network egress, browser environment, and profile behavior—stacking together, not 'using the same tool' itself. The key is whether the tool keeps an independent login environment and credentials for each store; if all stores share one egress and one set of credentials, the risk has nothing to do with the tool. For specific determinations, please refer to the platform's account notifications and official policies.
When platform subsidies cause final-price conflicts, should this be judged by the list price or the final price?
Record both metrics; they serve different purposes: price-change approval looks at the list price, while conflict assessment looks at the final price. Subsidies can create a large gap between two sites that have the same list price; this type of difference is a temporary platform behavior and should not be used as a reason to change the list price.
How should an agency operations team confirm pricing boundaries with the brand?
Only three things need to be written into the cooperation annex: the calculation method for allowed price differences, the rule of no price changes within overlapping windows, and the price-change approval chain and audit trail fields. What the brand wants is the answer to 'why the price difference exists,' not a unified price list.
