Explore safely
The public demo uses synthetic records to illustrate the ERP's shop, order, advertising and warehouse workflows. It is isolated from real business workspaces.
Product guide
From authorization to action.
Every connection has a named owner, an explicit permission and a visible destination. This guide describes the real ERP workflow, including the limits of each TikTok integration.
01 / Business access
Start with the right customer and shop.
Project Lighthouse can serve separate business customers. Visitors may register with a verified email to explore a synthetic-data demo tenant; this does not expose customer data or grant a real business account. Access to an operational workspace and its shops is reviewed and provisioned separately by that business's administrator.
Approved users
Authorized users sign in to their assigned ERP workspace through the identity options enabled for that business. Shop visibility and operational permissions depend on their assigned access.
One market, one connection
Each authorized TikTok Shop is kept as a distinct operating unit with its own platform shop identifier and market. A group view aggregates, but does not replace, these connections.
02 / Account connection
The account holder gives consent.
The ERP's marketing-account button starts TikTok Login Kit for the selected shop. A TikTok Shop seller authorization cannot substitute for this separate account authorization.
1
Choose the shop
The authorized user selects the shop and market in the ERP before connecting a marketing account.
2
Check the TikTok identity
The account holder signs in on TikTok's page and verifies that the account shown is the intended one.
3
Grant requested access
With consent, Login Kit returns a code. The server exchanges it for tokens; the ERP stores the account connection without exposing tokens to users.
4
Confirm or disconnect
The ERP shows the connected account. The owner can revoke access in TikTok or request disconnection.
Requested scopes: user.info.basic for account identity, video.list for public videos, and video.upload for an explicitly chosen inbox draft. Production use of these TikTok developer permissions remains subject to TikTok approval.
03 / Evidence
Keep video ownership verifiable.
Account identity and public video IDs are returned by TikTok for Developers. Shop-level orders, clicks and GMV are returned by the separately authorized TikTok Shop connection.
What the account feed can show
Public video identifiers, cover, description, publication time and available engagement fields for the consenting account.
What it cannot prove alone
A public video list does not establish which shop's product it promoted or the resulting sales. The ERP matches exact IDs where both permitted sources support the link and labels unmatched data clearly.
04 / Draft transfer
Upload is not publication.
When TikTok has granted video.upload and the account has consented, an authorized user selects one permitted video, checks the destination account, and explicitly requests transfer to that account's TikTok inbox.
A
Select
Choose a finished video the customer has rights to use and a connected TikTok account.
B
Confirm
Review the chosen account and video. The transfer starts only after the user's deliberate action.
C
Verify delivery
The ERP checks TikTok's processing status; a received task ID alone is not proof that the inbox received the video.
D
Finish on TikTok
The account holder handles the inbox item in TikTok. Project Lighthouse does not automatically publish it or use Direct Post.
Want to discuss access?
Business onboarding and reviewer walkthroughs are arranged through our team. Please do not email passwords or tokens.