A SnelStart integration connects your online administration to other software. An existing partner connector may be enough; a different process may need configuration or custom development. Before building, check the administration, how access is granted and who arranges developer credentials. Then define the actual work: which records should transfer and how failures will be recovered.
For the general approach, read connecting software. Our process automation checklist helps define the assignment before you compare suppliers.
What do you need to connect SnelStart?
SnelStart’s API guidance requires an online administration and confirmed subscription, beyond the free trial. Partner access often uses an integration key. Check these conditions before the trial.
Make a short inventory next. Which administration receives the records? Who can grant access? Which application provides the data? What document should ultimately appear in SnelStart? These answers allow the supplier to check the required operations.
What does the integration key do, and what must the developer arrange?
Separate customer access from developer access. You activate the connection for your administration. The developer must also arrange the appropriate registration and approval. A key working in your environment doesn’t establish that every production requirement has been completed.
The SnelStart developer portal describes a temporary developer account and certification before issuing a permanent custom or production key. Ask which procedure applies to your solution, who handles it and which dependencies affect the schedule. Product documentation checked on 2026-09-24.
Share an integration key only through the agreed secure route with the application that needs it. Keep it out of shared project documents and error messages. Establish who can end access when the supplier relationship finishes.
When does an existing partner connector fit?
Investigate an existing connector when it supports the required data and actions. Request a demonstration with your files. A connector might process sales data without handling the particular returns process used by your shop.
| Topic | Question for the demonstration |
|---|---|
| Customers | How is an existing contact recognised? |
| Products | Which product identifier connects the systems? |
| Invoices | Is an existing document transferred or a new one created? |
| Corrections | How are returns and changed amounts processed? |
| Failures | Where can an employee see what didn’t work? |
Ask which inputs are rejected as well. Rejection isn’t a flaw when it’s deliberate and visible. A clear error can be preferable to an automatic assumption that later requires an accounting correction.
A workflow platform is another possible route, provided the required actions and access are available. The distinction from custom automation concerns your process and maintenance, not simply whether someone writes code.
How should you test a webshop integration?
Don’t begin with every order at once. Choose examples that expose differences: an existing customer, a new product, a discount and a refund. Agree the expected result with your bookkeeper, then compare it with what the integration actually creates.
Consider a hypothetical shop using one product number for a kit while the accounts track individual components. The problem is the meaning of the identifier. First decide whether the kit should be one line or whether its components are required. Have the supplier implement the mapping afterwards.
Agree inventory behaviour too. Which system determines availability, which location counts, and when can a returned item be sold again? A two-way connection without an agreed source can reverse intentional changes. Request synchronisation only for information the process needs.
What happens after restoring a backup?
SnelStart says continuing in a restored administration requires reactivating the connection with the new key. Include this in the recovery plan.
Check progress information held outside SnelStart too. The integration might consider a document complete even though the restored administration no longer contains it. Restarting from scratch could instead offer records that already exist.
Test a recovery procedure with a clear stopping point. Compare the last processed source identifiers, find missing documents and agree who authorises replay. Keep a record of that exercise. It provides more evidence than simply confirming that a backup exists somewhere.
How do you arrange a bank connection?
SnelStart distinguishes its standard PSD2 connection from additional options offered by some banks. Those options can have different charges and terms. Use the official banking information to check the route for your account.
Assess banking separately from the webshop integration. Bank transactions, sales documents and payment-provider settlements may arrive at different times. Have your bookkeeper define reconciliation, especially where a provider deducts fees before paying out.
Assign someone to handle requests for renewed consent. At setup, also establish which period is retrieved automatically and which period still needs a file import. That helps avoid unexplained gaps or overlap.
What does a SnelStart integration cost?
Compare quotes for the same work. Separate subscriptions, configuration, development, testing and maintenance. Ask a partner connector supplier which support is included. For custom work, ask about registration, approval and any other service charges too.
Not every extension is simply another field. A different invoice process may need different error handling; a second administration requires new access and mapping decisions. Ask which requirements cause the most work so you can reduce or phase the scope deliberately.
Our software cost guide helps assess spending over a longer period. Include internal work: cleaning files, reviewing examples and training employees. A development quote doesn’t remove those responsibilities.
Which maintenance arrangements should you document?
An employee needs to see which documents require attention. Ask for alerts containing a recognisable source identifier and a clear reason. A technical error code without context offers little help to the daily operator.
Establish who corrects source data, who investigates technical failures and how retries begin. During acceptance, submit a previously processed document again. The outcome must be controlled, without an unintended duplicate entry.
Handover needs mappings, access arrangements and recovery instructions as well as code. The code TopDevs writes for your integration remains yours; SnelStart and other products have their own terms. Read code ownership and transferability for the questions to ask.
How do you actually get started?
Check the online administration and access route first. Collect examples of ordinary work and an exception. Have each candidate process them, then test resubmission and recovery after an interruption.
For system integration development, book a call. Include your current software, intended documents and the administration’s owner in the preparation.
