Introduction

Active Integrations

 

Integrations where our platform actively searches for information to make your order management a transparent action, requiring little or no action from the client.

  • BLING - https://www.bling.com.br/

  • TINY - https://tiny.com.br/

  • OMIE - https://www.omie.com.br/

  • MILLENNIUM - https://e-millennium.com.br/

  • MXM - https://www.mxm.com.br/

  • RADAR - https://wk.com.br/

  • ECCOSYS - https://eccosys.com.br/

  • VTEX - https://vtex.com.br/

  • PROTHEUS - https://totvs.com.br/

  • MICROVIX - https://microvix.com.br/

Details regarding each integration mentioned above. More technical data should be consulted directly in the registration of each connector or with the development team.

  • BLING – Plug and Play

  • The configuration is done through the creation of an application (by the client) and confirmation of the authorization URL which consists of https://oms.tpl.com.br/erp/bling/<client_id>

  • In this integration, the following data must be defined:

  • Day range for order reading (Note: filtering is by order creation date)

  • Whether client stock (in our platform) will be sent to the ERP

  • Whether we will fetch labels from the ERP

  • Whether tracking info and order status will be forwarded to the ERP

  • URL

  • Tracking Code

  • Order Status (Accepted, Ready for collection, In transit, Delivered, or Delivery failed)

 

  • TINY – Plug and Play

  • To configure this integration, the client must send the authentication token provided by Tiny for API access.

  • This integration features: Day range for order reading (filtering by creation date), Label reading, URL return, Stock update in ERP.

 

  • OMIE – Plug and Play

  • For data access, the client must send us: APP KEY, SECRET KEY. It is also necessary to define stages (check stage codes with OMIE): Reading, In transit, Delivered, Delivery failed.

 

  • Millennium – NOT Plug and Play

  • This integration requires the participation of a Millennium support team (or third parties) and is a charged service. Requirements include: New order filtering, Start of picking, Picking verification, Volumetric data return, Billing request, NFe request, Status and URL return.

 

Passive Integrations

Integrations developed by third parties to consume our API ecosystem to facilitate and automate the order management process.

  • NOTAZZ

  • OUR API – Here the client can create their own integration (https://oms.tpl.com.br/doc/read)

In this type of integration, the owner must receive credentials (APIKEY, TOKEN, EMAIL) to perform the configuration with the partner.