Case Studies

Challenge

As Poland's largest manufacturer of wheel balancing weights and diaphragms for pneumatic suspensions, TIP-TOPOL ships hundreds of orders a day to customers across Poland and Europe. Handling those orders meant logging in to the courier operators' panels by hand — DPD, InPost, GLS — copying address data, generating waybills and tracking shipment statuses in separate systems. At TIP-TOPOL's scale that meant hours of administrative work every day, a risk of mistakes, and delays in telling customers where their delivery stood.

Solution

With gravity.integration we connected TIP-TOPOL's Graffiti.ERP system directly to the logistics operators' APIs. The ESB data bus automates the entire process:

• Automatic waybill generation — order data from the ERP goes straight to the courier's system, with no retyping
• Real-time status updates — dispatch, delivery and problem notifications flow back into the ERP automatically
• Many operators handled from one place — DPD, InPost, GLS and Allegro connected through a uniform REST API
• Label printing from inside the ERP — the warehouse worker never leaves the system they work in

The deployment took a few days and required no changes to the company's existing IT infrastructure.

Challenge

Kapitan Navi uses the Roger access control system to record employees entering and leaving the production zones through RCP gates (turnstiles and interlocks). The Roger data accumulated in an MSSQL database, but analysing it meant manual exports, spreadsheet work and cross-checking against the ERP's records. Production managers had no quick view of actual working time, break lengths, or whether employees were clocking at the right gates.

Solution

gravity.integration connected the Roger system's MSSQL database with the Graffiti.ERP system's PostgreSQL database through two ESB projects:

• Real-time RCP data migration — raw data from the Roger readers is pulled every minute, filtered by the selected gates (turnstiles and interlocks) and written into the Graffiti database
• Automatic processing by a SQL algorithm — a SQL function processes the raw readings to the client's rules: classifying work and break periods, identifying entry and exit gates, totalling times
• Visualisation in the Grafbuilder module — the processed data lands in an analytics panel where the reviewer sees everything in one place
• Report generation — daily and detailed RCP reports available instantly, with export to Excel

Challenge

ELMET Poznań sells across many channels — orders arrive simultaneously from the BaseLinker platform, which handles the marketplaces and online stores, and directly in the Graffiti.ERP system. Without automatic synchronisation that meant retyping orders by hand, stock discrepancies, trouble pairing shipping and payment methods between the systems, and delays in telling customers how their order was progressing. With sales channels multiplying and delivery methods ranging from courier to personal pickup, manual handling was becoming the bottleneck of the whole process.

Solution

gravity.integration talks to the BaseLinker API, fetching orders, customer data and delivery methods, then processes them and writes them into Graffiti.ERP. The whole process runs fully automatically:

• Automatic order collection from BaseLinker — gravity.integration projects poll the BaseLinker API and fetch new orders together with their line items, address data and shipping method
• Intelligent shipping mapping — the Grafbuilder module pairs BaseLinker shipping methods with their Graffiti.ERP and WMS counterparts; missing methods are created automatically
• Automatic dictionary maintenance — when a business partner is missing in Graffiti, gravity.integration pulls their data from the VAT whitelist (NIP validation through the Graffiti DLL) and creates a new record
• Payment method pairing — missing payment methods are created automatically in Graffiti so they match the invoice
• Fulfilment feedback — the order's status in Graffiti (picking, dispatch, invoicing) flows back to BaseLinker in real time

Challenge

Multichannel sales on the cStore platform require constant, consistent data exchange with the Graffiti.ERP system. Orders, stock levels, price lists, product indexes and business partner data have to agree on both sides — otherwise you get discrepancies in product availability, out-of-date prices for individual pricing groups, and orders retyped by hand. B2B customers add extra complexity: every pricing group has its own terms, part of the assortment needs quantities reserved for specific partners, and a customer using the platform expects the full history of their orders — whatever channel they were placed in. As the number of partners and product indexes grew, manual synchronisation was becoming the sales process's bottleneck.

Solution

gravity.integration exposes a ready-made, externally published webservice (API) — with a set of methods the cStore platform calls directly. It is the external system that queries the gravity.integration API whenever it wants to push or pull data from Graffiti.ERP, which keeps the exchange consistent and controlled. The synchronisation covers (→ to cStore, ↔ two-way):

• Customer orders (↔) — adding the order header with its line items; in return cStore fetches all of a partner's orders regardless of channel (including those entered outside the platform), presenting complete information based on pricing groups (filter: the B2B partner list)
• Stock records — quantities (→) — sales plans by pricing group: calculating the reserved quantity for B2B customers in a given group and the free quantities available to everyone (B2B/B2C)
• Price lists (→) — pricing groups correlated with partner records and product indexes

The Grafbuilder module

The remaining data — and the orchestration of the whole process — is handled by the in-house Grafbuilder module. The synchronisation is completed by:

• Indexes and business partners (→) — pushed to cStore as the basis of the catalogue and pricing permissions
• Sales invoices (←) — invoice information with on-demand PDF download from the platform; the printout is generated in the Graffiti.ERP-compliant variant (through the DLL)
• Warehouse documents (←) — passed from Graffiti.ERP to cStore

Once an order arrives from cStore and its data has been processed, it lands in Graffiti.ERP. Grafbuilder builds the sales plans for B2B partners — together with the SQL views, triggers and functions (among them stock-limit checks and reservation priorities for orders).