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.