Catalog & listing control
Keep products, variants, pricing inputs, listing quality and campaign-ready catalog structure consistent with the brand's source of truth.
Managed TikTok Shop & Shopee Operations
D2 Group operates TikTok Shop and Shopee as a managed commerce function. We start with the recurring operating baseline, then add GMV Max, Affiliate/KOC, Creative Performance or deeper reporting only when the shop's constraint and economics justify them.
Primary offer
Managed marketplace operations
Platforms
TikTok Shop + Shopee
Growth modules
Ads + creators + creative
Commercial lens
GMV + verified economics
The operating baseline
The baseline is the recurring work that keeps the marketplace commercially operable. D2 can own this layer directly or share it with an in-house team through explicit responsibility boundaries.
Keep products, variants, pricing inputs, listing quality and campaign-ready catalog structure consistent with the brand's source of truth.
Own recurring Seller Center or Shopee operating work, platform notices, promotion readiness and the tasks that otherwise sit between teams.
Make order, stock, fulfillment, return and after-sales exceptions visible with an owner, next action and escalation path.
Coordinate marketplace campaigns, vouchers, pricing changes and product priorities without treating promotions as isolated calendar events.
Review marketplace performance on a fixed cadence with clear source data, operating issues and next commercial actions.
Marketplace execution
D2 can coordinate TikTok Shop and Shopee together, but does not flatten their catalog rules, campaign mechanics, advertising, fees, settlement or fulfillment behavior into one generic playbook.
TikTok Shop
Seller Center, catalog, campaigns, shop health, fulfillment exceptions and reporting, with GMV Max, Affiliate/KOC and creative connected when they are part of the operating scope.
Shopee
Catalog, pricing, vouchers, campaigns, Shopee Ads coordination, shop-health issues, fees and profitability controls managed around Shopee-specific operating rules.
Where should the engagement start?
The same marketplace needs different work depending on whether it is being launched, taken over, plateauing or producing numbers the business cannot reconcile.
Start with the current catalog, campaigns, data, team responsibilities and constraints. D2 maps what should remain, what is leaking and which operating responsibility should change first.
Set up catalog structure, pricing, promotions, shop-health routines, approval paths, reporting and ownership before scaling Ads, creators or campaigns.
Review traffic, conversion, stock, creator supply, creative, Ads efficiency and SKU economics together so the next action targets the real bottleneck.
Reconcile marketplace revenue with platform fees, Ads, creator cost, COGS, settlement and other verified inputs so topline growth does not hide contribution leakage.
Growth modules
Paid media, creators, creative and reporting are not the definition of Commerce Operations. They are modules D2 can add to the managed baseline when they solve a specific commercial constraint.
Commercial control
When verified source data is available, D2 connects marketplace revenue with platform fees, advertising, creator commission, COGS, settlement and other variable inputs. The goal is not to manufacture one perfect number, but to make the next decision economically defensible.
Scale
Increase the growth input when demand, stock, conversion, creative supply and contribution headroom support it.
Hold
Keep the current level when the system is producing acceptable economics but the next constraint is not yet resolved.
Fix
Correct catalog, pricing, stock, shop-health, fulfillment, fee or conversion leakage before asking paid growth to compensate for it.
Retest
Change one meaningful variable, define the expected signal and review again instead of making several untraceable changes at once.
Ownership boundary
The engagement works when both sides know which decisions stay with the brand and which recurring responsibilities D2 is accountable for operating.
Client retains
D2 owns in scope
Operating cadence
Map the current shop, data, people, access, constraints and economics before changing campaigns or adding another growth tool.
Set explicit responsibility for execution, approvals, data, Ads, creators, reporting and exceptions so work is not duplicated between teams.
Run the recurring marketplace baseline and coordinate growth modules against current product, inventory and commercial priorities.
Bring marketplace, advertising and verified cost inputs together so GMV can be separated from contribution and operational leakage.
Scale, hold, fix or retest based on the constraint that is actually limiting the shop instead of reacting to one headline metric.
First-party commerce evidence
These D2-owned case pages are implementation evidence. They show how catalog, growth, creators, logistics and economics were handled in real operating contexts.
TikTok Shop operations, GMV Max and commercial reporting with revenue, advertising, platform fees, COGS and SKU economics reviewed together.
A US-market commerce case where livestream execution had to work inside distributor, logistics and local operating constraints.
Multi-SKU food commerce where catalog, fulfillment reality, product cost and marketplace execution had to stay aligned.
Creator commerce and structured creative testing connected to product positioning, marketplace growth and recurring production decisions.
Commerce knowledge graph
How to connect marketplace growth with contribution and unit economics.
Read moreWhy topline GMV can move differently from economic result.
Read moreWhy advertising efficiency is not the same thing as SKU profitability.
Read moreFirst-party technology proof for marketplace reconciliation, cost visibility and recurring commercial control.
Read moreCommercial model
D2 does not automatically default every marketplace engagement to a percentage of total marketplace revenue. The base commercial model is defined around marketplaces, responsibilities and workload. Any threshold, incentive, performance term or additional module is made explicit in the proposal before work starts.
Recurring operating responsibility and workload are defined first.
GMV Max, Affiliate/KOC, Creative Performance or deeper reporting are added when justified.
Performance thresholds, incentives or other commercial terms are agreed before execution.
Commerce Operations FAQ
Managed Commerce Operations means D2 takes explicit recurring responsibility for an agreed marketplace operating layer rather than only delivering isolated campaign tasks. The baseline can include catalog and listings, shop health, promotions, orders, inventory and fulfillment exceptions, after-sales and recurring reporting, with growth modules added only where they are in scope.
D2 can operate TikTok Shop and Shopee across catalog and listings, pricing and promotions, shop health, orders and fulfillment exceptions, campaign execution and recurring reporting. Growth modules can include GMV Max, Affiliate/KOC, creative performance and deeper commerce reporting when the operating constraint and economics justify them.
Yes. D2 can take over an existing shop without assuming the current setup must be rebuilt. The first step is to map the catalog, campaigns, data sources, operating responsibilities, current constraints and approval paths, then define what D2 should own and what should remain with the client.
Yes. D2 can manage TikTok Shop and Shopee as one coordinated commerce function while preserving the different catalog, campaign, advertising, settlement, fulfillment and platform rules of each marketplace.
No. Paid growth is not the operating baseline. D2 can own marketplace execution first, then manage GMV Max or other paid activity as a connected growth module so Ads decisions are tied to product priorities, stock, conversion, creative supply and SKU economics.
D2 starts from the operating constraint rather than one headline metric. The review can include catalog structure, pricing, stock, traffic, conversion, shop health, Ads, creators, creative supply, fees and SKU economics, then prioritizes the issue most likely to change the next commercial decision.
D2 reviews marketplace health, traffic, conversion, average order value, order and refund signals, advertising efficiency and creator performance. When verified source data is available, D2 also brings platform fees, advertising, creator costs, COGS and other variable costs into a contribution or profitability view instead of relying on GMV or ROAS alone.
Yes. D2 can own one marketplace, a missing operating layer or selected growth modules. The engagement is structured around explicit ownership for execution, decisions, approvals, data and exceptions so responsibilities are not duplicated between D2 and the internal team.
D2 does not automatically default every Commerce Operations engagement to a percentage of total marketplace revenue. The base commercial model is defined around operating scope, responsibility and workload. Any fixed fee, performance threshold, incentive or additional commercial term is stated in the proposal before execution.
D2 works with businesses in Vietnam and international markets. The delivery model depends on marketplace availability, local logistics, account permissions, creator access, language requirements and the operating scope that can be owned reliably in each market.
Next step
Share the current shop, marketplace, team setup and operating problem. D2 can use that context to define a bounded first scope instead of forcing the account into a generic package.