01 / Data model
Define systems of record and required fields.
Source
01Data02Workflow03Approval
KG-NET / ERP integrations
Maintain data once. Share it reliably.
Planning, design and technology are considered together. Scope and price follow your actual requirements.
01Data02Workflow03Approval
ERP integrations
How it comes together.
Three perspectives on your project. Scroll through the process or select a step.
02 / Mapping
Align identifiers, status and formats.
Interface03 / Synchronisation
Test retries and conflicts.
DestinationWORKING TOGETHER
Clearly agreed. Clearly delivered.
A defined scope
Before work begins, we agree goals, content, responsibilities and integrations. You know what is included and what needs a separate plan.
Reviewable milestones
Structure, design and function are reviewed in clear stages. Decisions follow your requirements and feedback.
A clear handover
The agreed scope defines access, guidance and an understandable operation and maintenance plan. Ongoing support is agreed explicitly.
ERP integrations: Keep stock, product and order data consistent across your store and ERP.
What we build with you
Products, customers and orders need clear systems of record. We define ownership, mapping and synchronisation rules, including conflicts, so a connection does not simply spread errors between systems.
- Data mapping
- Synchronization rules
- Error and conflict handling
- Traceable logs
ERP integration needs clear data ownership. Product codes, stock, prices and orders receive explicit mappings and update directions. Conflicts, retries and missing values are planned. A failed transfer must not create duplicate orders. Field mappings and test cases are reviewed with responsible staff before live exchange; assumptions about external systems must not silently become business rules.
How the project takes shape
Data model
Define systems of record and required fields.
Mapping
Align identifiers, status and formats.
Synchronisation
Test retries and conflicts.
What makes working with KG-NET clear
We discuss how your business actually works before specifying individual features. Dependencies, responsibilities and the agreed scope are documented. Decisions are discussed using actual pages, tasks or data flows. Questions, materials and approvals are coordinated with an accountable contact. During handover we clarify what your team can maintain and which technical work requires a separate service. You can see what was agreed and where an additional decision is needed.
20 / QUESTIONS & ANSWERS
Decide with clarity.
How are interfaces selected?
We review documentation, permissions, data fields and operational limits. A stable supported API is preferable to unclear access.
Who decides in automated workflows?
Approval points are explicit. Purchases, sensitive changes and payments do not proceed unchecked on an AI decision.
What happens if an API fails?
Errors are recorded and retries limited. Last known data carries a timestamp and missing data is not invented.
How is duplicate processing avoided?
Unique event identifiers and defined state changes help handle retries safely. Typical failure scenarios are tested.
Can barcode and QR workflows be integrated?
Yes, if scanners, identifiers and the target system align. We clarify whether a code represents a product, batch or process.
Where is AI useful?
In bounded tasks such as suggestions or classification whose quality can be assessed. Data access and human review stay explicit.
How are secrets stored?
Tokens and keys belong in protected server-side storage. They are not exposed as browser data or unprotected text fields.
Can the system be extended later?
Modules and documented interfaces limit dependencies. Extensions are checked against the data model, permissions and existing workflows.
How does the project start?
We clarify the audience, existing systems, responsible people and intended outcome, then agree the scope.
What determines the price?
Scope, integrations, content, licences and support are considered separately. You receive an individual offer before delivery starts.
When is the schedule agreed?
After discovery and prioritisation we agree milestones. Approvals, access and external dependencies influence dates.
Who supplies content and access?
We agree which text, images and data you provide. Access should use roles, invitations or limited tokens wherever possible.
Can existing systems keep running?
Yes, subject to a technical review. We plan changes, backups and rollback paths to keep the transition controlled.
How are changes agreed?
Questions are collected in the project. Extensions get a defined scope and approval before additional implementation.
How is acceptance handled?
We agree concrete test cases and responsible people. Open issues are documented and release follows the agreed approval.
Is a handover session included?
Handover can include training, documentation and defined access rights. The scope and format are specified in the offer.
What happens after launch?
Support, updates and response times are agreed separately, making internal and KG-NET responsibilities clear.
How is personal data handled?
We limit access and review data flows, retention and processor arrangements. Legal approval remains with the controller and their advisers.
Can you work across borders?
We work with businesses in Austria, Germany, Switzerland and Serbia. Language, responsibilities and actual market needs are agreed together.
How are outcomes assessed?
We agree verifiable goals and identify the data source. Without connected measurement there are no invented metrics or guaranteed outcomes.
Plan the connected services together
Depending on your project, we align this service with related areas. Content, technology and responsibilities should fit together. Discuss the interfaces and actual scope you need with us:
THE NEXT STEP
Your idea. A clear plan.
Tell us what you want to change. We will clarify goals, scope and the right approach, with an individual proposal.
KG-NET
Ilija Benjak
Völkermarkter Straße 280
9020 Klagenfurt am Wörthersee
Austria