Frequently asked questions
VELUMA Commerce ERP · Draft — not yet in effect · 中文版
Short answers to common questions. The privacy policy gives the details: Privacy policy · 隐私政策.
What does VELUMA Commerce ERP do?
VELUMA Commerce ERP is a read-only order management application for cross-border (SEMI) sellers on the TEMU US site. It shows a store's TEMU US orders (parent and child orders, items, status and key times), synced read-only from TEMU. Orders can be filtered by store and status, and the sync status of each store is shown. Staff who hold an individual recipient-data grant can view one order's shipping recipient on demand, for a stated purpose; every view of recipient details is recorded.
Who is it for?
The application currently works with TEMU US-site stores of cross-border (SEMI) sellers, and is used by those sellers and their staff. It is a business tool: accounts are created by our administrator (see the next question).
How is a store connected?
Accounts are created on request by our administrator; there is no self sign-up, and seller accounts never hold administrator rights. The seller authorises the app in the TEMU Seller Center (agentseller) and hands the access token to our administrator over a secure channel; the administrator enters it, it is verified and stored encrypted, and it is not shown again after it is saved. Access to recipient details is granted per person by our administrator, only on the seller's written request.
Which TEMU data does it read? Is it read-only?
Yes, it is read-only. The application calls only these read-only TEMU Open API interfaces; no write API is used:
bg.open.accesstoken.info.get: to verify a token our administrator enters.bg.order.list.v2.get: order sync, operational order fields only. Recipient details are not fetched during order sync.bg.order.decryptshippinginfo.get: only when a staff member who holds the recipient-data grant chooses a purpose and clicks “Show recipient” for one order. Every view of recipient details is recorded, and new fetches from TEMU are limited to 30 per person and 200 per store per hour.
Of the recipient details TEMU returns, the application keeps only name, phone number, address line 1, address line 2, address line 3, postcode, region name 1, region name 2, region name 3, region name 4, encrypted. The other fields are discarded and never stored.
Can it change anything in my store?
No. The application never changes anything on TEMU: it only sends TEMU read-only requests, using the store's access token.
How long is information kept, and where is it stored?
Recipient details are scheduled for deletion 30 days after TEMU reports the order completed (canceled or received). If TEMU has not reported the order completed within 90 days of its creation time, they are scheduled for deletion 90 days after creation. These deadlines apply to the application's database; copies in backups remain until those backups are deleted. The hosting provider has not yet confirmed how long it keeps its automatic backups; what it has told us about deleting them is in section 9. Other information is kept for different periods, and some of it has no automatic deletion yet.
The application server is in the United States. The hosting provider also keeps automatic backups of the whole server, which we cannot switch off. It stores them in several of its data centres, which can be in more than one country, and we cannot limit them to one country. The provider has not yet confirmed which countries are involved. These backups contain the database and the keys used to encrypt recipient details and store access tokens. Where the information is processed, including those backups, is described in section 8 of the privacy policy, and how long each kind of information is kept in section 9.
How do I end the authorisation or ask for deletion?
The store's access token is kept until our administrator deletes it; ask us to delete it (see the contact details below). That removes it from the application; copies in backups remain until those backups are deleted. To end the authorisation at TEMU, the seller should also cancel it in TEMU Seller Center.
People who use the application can ask us to close their account. We close an account by disabling it and removing its grants; the username and activity logs are kept for security. Recipients of TEMU orders should contact the seller they bought from, or TEMU. See section 11 of the privacy policy.
How do I contact you?
VELUMA Commerce ERP is operated by SAGE HOUSE WARES INC.. Write to us at Gaoyiyao3@gmail.com. We answer requests without undue delay.