Data reaches the right place.
Every object has a known source and recipient.
Every object has a known source and recipient.
The exchange removes only duplication that actually needs removing.
The team learns about missed events and how to continue safely.
One business action has a clear result in both systems.
Owns the agreed fact and event identifier.
Agreed fields, direction and access.
Verify the actual record change.
Return the confirmed result with the source event identifier.
A repeated message must not create another order, refund or email.
Keep the state visible and agree recovery.
Example: an accepted order changes the receiving system. If a message is retried, it must not become a second order, refund or email; unresolved errors go to the agreed responsible person.
A verified connection with documented data rules, error handling and responsibility for ongoing operation.
Review the systems, available interfaces and data quality.
Agree the source of truth, mappings, access and allowed actions.
Connect a focused flow and test normal and failure scenarios.
Verify records and hand over monitoring and recovery instructions.
An order is sent twice. A price changes on the website but not in the proposal.
A shared email merges different people. A provider accepts a payment but the response is lost. These situations cannot be fixed by a single promise of real-time synchronisation.
We start with rules: which system determines the value, exactly what is transferred, when a change is confirmed and who handles exceptions.
We establish where products, contacts, orders and financial documents are managed.
We agree identifiers, required fields and relationships. We do not merge different entities merely because their names are similar.
We check available interfaces, licences, permissions, limits and data.
We select an API, event, batch exchange or controlled import for the actual need. A manual start with confirmation can be more sensible than a complex unverified integration.
We distinguish prepared, sent, accepted, rejected and unknown outcomes.
A retry must account for an action already performed. When a response is lost, we first reconcile state rather than automatically create a second order or payment.
We prepare useful logs without unnecessary personal data, delay alerts and a way to reconcile results.
The team can see what needs attention and how to continue. A technical response code does not replace checking the business object.
An academy connects sales and learning.
Customer, payer and learner are transferred as different roles. A confirmed payment creates only the agreed basis for access; allocation of corporate places and cancellation of participation are checked separately.
We agree examples and exceptions before implementation.
We check normal transfer, retry, service unavailability, invalid data and a lost response. Correction of an already transferred record and stopping the exchange are considered separately. Real external effects occur only in an authorised test or working scenario.
After launch pNet helps support the connection: track interface changes, investigate discrepancies and refine rules.
System and data owners remain defined; integration does not remove their responsibility.
A map of objects and sources, agreed transfer rules, a way to check results and instructions for exceptions.
It is clear which data moves, what stays in place and where a person is needed.
| Event | An enquiry arrives |
|---|---|
| What counts as a result | The correct CRM record is created and an owner assigned |
| What to do on failure | Reconcile the original request before resending |
| Event | An order is confirmed |
|---|---|
| What counts as a result | The accounting system receives the correct identifier and contents |
| What to do on failure | Check the main record in the agreed system; prevent a second order |
| Event | A status changes |
|---|---|
| What counts as a result | The recipient receives an allowed change |
| What to do on failure | Record the conflict and refer it to a person |
For a supplier, a catalogue enquiry can become a proposal, then an order and shipment.
At an academy, registration and payment do not yet mean a place has been assigned to a specific participant. pNet selects one authoritative record, documents field mapping and transfers only events that are actually needed.
Failures matter especially: an external service may have performed an action while its response was lost.
A retry must not become a second order, refund or email. We provide an operation identifier, retained state and a way to determine the result without a blind retry. API, plan, permissions, provider limits and the right to change records are checked before implementation.
CRM handles business stages; process automation can connect agreed steps; and monitoring helps reveal and investigate errors.
Without an API, an honest manual stage is better than a fictitious seamless integration.
All pNet business systems.
Availability depends on external APIs, permissions and provider limits. Historical migration and changes to connected systems are separate scope.
Describe your systems, the problem and any known constraints. You do not need a complete technical specification. Please leave passwords, keys and customer data out of your message.
That depends on its available interface, permissions, licence and provider terms. We check compatibility before promising a ready connector.
Acceptable latency is determined by the process. Interface capabilities and system limits are checked separately; real time is not assumed by default.
Sometimes, for a limited set. Relationships, history, attachments, permissions and identifiers may need another method. A file format does not prove a complete migration.
No. With an unknown outcome, retrying can create a second effect. State checks and suitable reprocessing rules are needed.
Tell us where information comes from and goes, who corrects it and what happens on failure. We will choose a useful scope and verifiable rules.