01 / Business rules
Record customer groups and pricing logic.
Product
01Product02Basket03Order
KG-NET / B2B systems
Business customers need suitable processes.
Planning, design and technology are considered together. Scope and price follow your actual requirements.
01Product02Basket03Order
B2B systems
How it comes together.
Three perspectives on your project. Scroll through the process or select a step.
02 / Access model
Separate companies, staff and approvals.
Basket03 / Order flow
Connect enquiry, offer and purchase order.
OrderWORKING 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.
B2B systems: Business customer workflows with company accounts, approvals and pricing rules.
What we build with you
B2B often involves individual catalogues, pricing and approvals. We plan company accounts, employee access and purchasing journeys around internal rules so the interface matches actual sales operations.
- Company and user accounts
- Custom pricing logic
- Order approvals
- Documents and interfaces
B2B systems distinguish organizations, users and permissions. A company may have several contacts with different responsibilities. Customer terms, approvals and document access follow this model. Public product information remains separate from internal pricing. Every integration must preserve the correct customer context; hiding a menu item alone does not enforce access control.
How the project takes shape
Business rules
Record customer groups and pricing logic.
Access model
Separate companies, staff and approvals.
Order flow
Connect enquiry, offer and purchase order.
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.
Which shop platform fits?
Catalogue size, B2B rules, payments and integrations guide the choice. WooCommerce is an option, not an automatic requirement.
Can products have variants?
Yes. Attributes such as size or version are modelled with unique item identifiers. Prices and stock need clear ownership.
How are payments integrated?
Through authorised payment providers and supported interfaces. Fees, countries and approval processes are reviewed first.
Can the shop connect to an ERP?
If a suitable interface exists. We define data ownership, synchronisation direction and error handling.
Can customers have individual B2B prices?
Yes, with explicit rules for customers, groups and discounts. Access is checked server-side rather than hidden visually.
How are inventory conflicts handled?
A designated stock system and rules for reservation, reconciliation and retries prevent contradictory updates.
Can an offer precede an order?
A quotation process can include review and client approval before ordering. Binding prices follow the agreed rules.
What is tested at checkout?
Inputs, shipping, taxes, payment callbacks and error messages are checked against agreed test cases.
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:
Confirmed projects from our work
These references show the confirmed scope of work. Your goals and workflows determine the right solution for your business.
ANKA
A custom commerce system with B2B features, bespoke plugins, portals and systems built around the client’s requirements.
Explore project and scope ↗TopMatic
B2B systems and client purchasing, shop, website design, invoice and accounting workflows, and local SEO.
Explore project and scope ↗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