Skip to content
Tejobit
Primavera logo

Billing

Primavera ERP integration

Orders, customers, prices and stock exchanged between Primavera ERP and your store, B2B portal or CRM through the Web API.

Request this integration See all integrations

Overview

Primavera

Primavera ERP, now Cegid Primavera, is one of the most widely installed ERPs in Portuguese mid-sized companies, covering sales, purchasing, inventory, treasury, accounting and HR, usually on the company's own server or a dedicated host.

In version 10, integrations go through the Web API, a REST interface running on IIS, either on the client's server or a dedicated machine with access to the ERP. Authentication is token based with a short lifetime (20 minutes by default), and each session should be logged out when finished; otherwise sessions can stay locked in the ERP database. The Web API can also be extended with custom .NET endpoints.

Tejobit designs around those constraints: an intermediate service that reaches the Web API over a secure channel, batches requests, manages tokens and sessions, and logs every operation. The ERP remains the source of truth and the certified software that issues and reports documents to the AT.

Use cases

What it is for

  • A B2B portal where trade customers see their own prices and place orders that land in Primavera.
  • A web shop publishing ERP stock and prices and sending orders back for invoicing.
  • A sales team in Salesforce seeing each customer's balance and invoices without ERP access.
  • A warehouse running its own logistics software that needs orders in and shipments back.
IN

What the connection listens to

  • An order placed in the web shop or B2B portal.
  • A won opportunity or new account in the CRM.
  • A scheduled sync of items, prices and stock from the ERP.
  • A shipment confirmation from the warehouse system.
OUT

What the connection does

  • Creates customer orders in the sales module, in the right company and series.
  • Creates or updates customer entities from CRM data.
  • Reads items, price lists and per-warehouse stock for use outside the ERP.
  • Exposes customer balances and documents to the portal or CRM.
  • Calls custom endpoints when the standard Web API does not cover an operation.

How it works

From the request to a working connection

  1. 01

    Request

    The form names the integration, the tools involved and what should happen in each case.

  2. 02

    Review and proposal

    Tejobit confirms what the API allows and sends a proposal with the flow, the price and the timeline.

  3. 03

    Setup and testing

    The connection is set up with the business's own accounts and tested with real cases before it goes live.

  4. 04

    Maintenance and monitoring

    Tejobit hosts the connection, follows up on errors and adapts it when the API changes.

The connection runs on Tejobit's infrastructure. The monthly fee covers hosting, monitoring and API changes.

What to prepare

  • Primavera ERP v10 with the Web API installed and configured on IIS.
  • Confirmation from the company's Primavera partner that its licence covers the intended Web API use.
  • Secure network access to the Web API server (VPN or protected publishing).
  • A dedicated ERP user for the integration, limited to the companies and modules it needs.
  • A mapping of series, warehouses and price lists per channel.

For security, do not send passwords, API keys or tokens through the form. Credentials are requested through a secure channel when the setup starts.

Limits

  • The Web API runs on the client's infrastructure, so the connection is only as available as that server and network.
  • Short-lived tokens and sessions that must be closed call for a well-built intermediate service; direct store plugins tend to break here.
  • ERP version upgrades may need retesting, especially where custom endpoints exist.
  • ERP customisations (user fields, extensions) must be known at the start to be included in the mapping.

Frequently asked questions

Before you start

Can an office-hosted Primavera talk to a cloud web shop?

Yes. The intermediate service reaches the Web API over a secure channel, and the shop never touches the ERP server directly.

Why does this cost more than an online invoicing integration?

It involves the client's infrastructure, more objects (orders, prices, stock, entities) and session and security handling that take more ongoing maintenance.

Does Tejobit replace the company's Primavera partner?

No. The partner stays responsible for the ERP, licences and customisations. Tejobit looks after the connection between the ERP and other systems.

Related integrations

See all integrations

Set up the Primavera integration?

Describe what should pass between the tools. The reply confirms feasibility, price and timeline.

Talk about your project geral@tejobit.com