← All articles

Blog

Odoo Customer Data from Marketplaces: What You Can Collect

Connecting Shopee, Tokopedia or Lazada orders to Odoo? Learn which buyer details marketplaces pass on, what is masked, and how Indonesia's PDP law applies.

6 min read
  • mid
  • odoo
  • marketplace

If you sell on Shopee, Tokopedia, Lazada or TikTok Shop and want a “customer database” in Odoo, here is the short answer: you will get the order and what is needed to ship it, but you should not expect a full marketing-ready customer list. Marketplaces treat buyers as their own customers, and they are tightening what they pass to sellers and to the software connected to them.

This article is a business explainer, not legal advice. Rules in this area change often, so check the points below in your own seller center before you design anything around them (context: October 2026).

The short version

  • You can usually get: the order itself (items, amounts, status), the shipping details needed to fulfil it, and the courier and tracking information.
  • You often cannot get: a buyer’s full name and phone number in readable form, an email address, or permission to use any of it for marketing outside the marketplace.
  • The trend is toward less data, not more. Plan your Odoo setup around orders and products, not around owning the buyer relationship.

What marketplaces are doing with buyer data

Each platform handles this differently, and the details move. What we could confirm from public sources:

  • Shopee: a seller-software help page states that Shopee masks the buyer’s name and phone number when an order is created, for all sellers, including those using third-party software. The same page says the buyer address is not masked, so it can be used to match orders. See this help article. That page comes from a software vendor, not Shopee, so confirm the current rule in Shopee’s own seller documentation.
  • Lazada: a seller-tool vendor’s notice says that from 1 July 2026 the Lazada Open Platform masks buyer name, phone and delivery address in order data retrieved through its API, with an exemption that sellers delivering with their own fleet can apply for (Zetpy notice). Verify the details in your Lazada seller center.
  • TikTok Shop (now closely tied to Tokopedia): a third-party article reports that recipient details can be redacted when TikTok handles the shipping label, and that TikTok’s seller policy restricts using customer personal information for anything other than fulfilling orders (Hubfluence). We did not find an official Indonesian rule for Tokopedia or Blibli on what a connected ERP receives, so ask the platform or your connector provider directly.

The pattern is consistent: platforms limit what leaves their ecosystem, partly for privacy and partly to keep the customer relationship on-platform.

What this means for Odoo

Odoo can store contacts, and a connector can create a contact for each order. But what lands in that contact depends on what the marketplace sends. In practice:

What you wantRealistic outcome
Orders, products and stock in one placeYes, this is the main benefit
Delivery details to ship and reconcileUsually yes, sometimes masked or partial
A clean list of repeat customersOften hard: masked names make matching unreliable
Email or WhatsApp marketing listsGenerally not from marketplace data
Customer lifetime value by personLimited; better measured by SKU, region or channel

A common mistake is creating one Odoo contact per marketplace order. With masked names, you end up with thousands of near-duplicate or meaningless contacts. A cleaner approach is often one generic “Shopee customer” style contact per channel, with the marketplace order number as the reference, and real customer records only where you collect the data yourself.

Where you can legitimately build a customer base

You can hold full customer records when buyers give you their details directly and know how you will use them:

  • B2B and distributor accounts you invoice yourself.
  • Your own website or WhatsApp orders.
  • Warranty or registration forms, loyalty sign-ups and in-store sales.
  • Customers who contact you for after-sales service and consent to being contacted.

A practical tactic some sellers use is a package insert inviting buyers to join a warranty or loyalty programme. Check that the invitation itself complies with each marketplace’s seller policy, because some prohibit steering buyers off-platform.

Indonesia’s PDP law in plain terms

Indonesia’s Personal Data Protection Law (Law 27 of 2022) was enacted in October 2022, and its two-year transition period ended on 17 October 2024 (CMS summary, Norton Rose Fulbright). Law firm summaries describe obligations for anyone who decides how personal data is processed, including:

  • Having a lawful basis, such as consent, for processing.
  • Notifying affected people and the authority of a data breach, reported as within 72 hours.
  • Possible administrative sanctions, and criminal penalties for certain misuse.

Sanction details are not spelled out in the summaries we reviewed, so check the statute or a lawyer. The dedicated supervisory authority was still to be established by presidential regulation in the law firm summaries, so confirm the current position.

For an Odoo user this means: know which personal data you hold, why you hold it, who in your team can see it, and how you would delete it. If you are an Odoo.sh or self-hosted user, you control the database and carry that responsibility. Odoo’s standard contact data can be edited or archived, and community modules such as the OCA “Right to be Forgotten” exist for anonymising contacts (the listing we checked was for Odoo 19.0), but check version compatibility and test on a copy first.

What goes wrong in practice

  • Treating masked data as real. Invoices or delivery documents showing “J***s” confuse staff and customers. Decide upfront which documents need real names and where they come from.
  • Duplicate contacts. Matching on masked name or phone creates mess. Match on order number instead.
  • Over-sharing internally. Every Odoo user who can open Contacts can see buyer addresses. Restrict access by role.
  • Keeping data forever. Some platforms set retention limits for buyer data. We could not confirm specific periods from public sources, so check each platform’s policy yourself.
  • Using marketplace data for marketing. This can breach both platform policy and the PDP law. Marketplaces can suspend accounts for it.
  • Policy changes mid-project. A connector that worked last quarter may start receiving masked fields. Ask your provider how they handle changes, and budget for maintenance.

Before you start

  1. List what you actually need the buyer data for (shipping, invoicing, returns, tax).
  2. Check your seller center and your connector’s documentation on what is sent.
  3. Decide how Odoo contacts will be created for marketplace orders.
  4. Set user access and a retention routine.
  5. Build your first-party customer channels separately.

If you want help deciding what to store in Odoo and how to set up the data flow, we are happy to talk it through.

Talk to us

If you are planning an Odoo and marketplace setup and are unsure how to handle customer data, Teknologia Solutions can review your channels and recommend a sensible approach. No charge for the first conversation, and no obligation.


Sources: Shopee order masking help article (seller-software vendor); Zetpy: Lazada buyer data masking notice; Hubfluence: TikTok Shop customer data; CMS: Indonesia PDP Law; Norton Rose Fulbright: PDP Law highlights; OCA Privacy Partner’s Right to be Forgotten. Several sources are third-party summaries; verify against marketplace seller-center documentation, the PDP law text and a qualified lawyer before acting.