We connected About You marketplace sales with BaseLinker operations: products and stock flow to the marketplace, while orders and their statuses flow into BaseLinker. The solution also includes product translations through ChatGPT on the client’s account, cached results and translation storage in a selected base.com field.

What problem did the client need to solve?

The client was developing marketplace sales and needed a consistent data flow between About You and BaseLinker. Catalog management, availability and order handling had to form one process. Product translation was a separate requirement: the client wanted to use their own ChatGPT account without paying repeatedly to translate identical content.

What did we implement?

Products and stock: BaseLinker → About You

We built a product publishing mechanism from BaseLinker to About You and added stock synchronization. This allows the catalog to be managed in BaseLinker, with listings and availability passed to the marketplace.

Orders and statuses: About You → BaseLinker

We enabled order imports and order-status synchronization from About You into BaseLinker. The team can handle these orders in one panel instead of manually copying them from the marketplace.

ChatGPT translations, caching and storage in base.com

Automated translations use the client’s account. We implemented result caching so identical content does not need to be translated repeatedly. Completed texts are also saved in the base.com field selected by the client, keeping them available within the catalog management workflow.

Caching reduces repeated translation-service requests, while saving the results in the client’s system makes completed content available for reuse.

What should you prepare for a similar implementation?

When planning a new integration or taking over work already in progress, prepare the following information to help define the scope:

• Launch status: is the About You seller account active, and have the first products been submitted for review?
• Data sources: where do products and stock levels originate, and which system should be authoritative for each type of data?
• Catalog: which identifiers, variants, attributes, images and descriptions are available, and what is still missing?
• Order handling: which statuses and changes does the team need, and where should they manage them?
• Translations: which fields and languages are included, where should results be stored, and who reviews them before publication?
• Existing work: what already works, what reports errors, and where does the team need help with configuration or day-to-day operation?

The store platform matters just as much as the marketplace and integration platform. For a similar project, we first review the complete data flow rather than assume selecting a connector resolves every issue.

How should you verify an integration?

A product appearing on the marketplace does not validate the entire process. Acceptance checks for a similar solution should cover publishing a product with variants, changing availability, importing an order and mapping its statuses. Translation checks should cover the language, destination field, saved result and behavior when processing the same content again.

Agree the scenarios and testing method for the specific account and the platforms’ current capabilities. This establishes what correct operation means for that workflow and which situations still need to be handled.

What did this implementation deliver?

The client received product and stock flows from BaseLinker to About You, with orders and statuses flowing in the opposite direction. Cached translations saved in base.com complement catalog handling. The team can process marketplace orders in BaseLinker and reuse completed translations without manually transferring them between systems.

Need to implement or improve an integration?

We develop applications and integrations tailored to business processes. If your solution is already partly configured, our technical support service can help establish the scope of diagnosis and further work. Include any training needs in your initial inquiry.

Describe your store platform, current configuration and required data flow through our contact form. Do not include passwords or API keys in the first message. For another example of connecting business systems, see our PrestaShop–WAPRO integration.