Keep Sitedish and CSV-export updated automatically.
Today you open your shop’s admin, look at which orders came in and carry them over. With this connector, what happens in Sitedish lands in CSV-export by itself, in the shape CSV-export expects. Request it and you get access; you hear from us within 24 hours.
What this connector takes off your hands
-
Today you open your shop’s admin, look at which orders came in and carry them over.
-
Today you create the task or the row yourself, or you just remember it and that fails eventually.
What Sitedish to CSV-export saves you
- Turn every new Sitedish order into a CSV-export task automatically.
- Turn every refund in Sitedish into a CSV-export task automatically.
- Turn every new Sitedish customer into a CSV-export task automatically.
- Turn every stock change in Sitedish into a CSV-export task automatically.
What travels across the link
Everything this connector moves between Sitedish and CSV-export, and how often.
-
Tasks
to CSV-export automaticallyThis lands in CSV-export as a task in the list or project you choose, so follow-up does not depend on someone remembering.
-
Rows
to CSV-export automaticallyThis arrives in CSV-export as a new row, so your overview stays complete without you retyping anything.
What each side expects
Sitedish and CSV-export do not describe the world the same way. This is what has to line up.
CSV-export
A task list or table wants to know where something belongs, and only stays usable with a fixed layout.
Setting it up
- 01
Request the connector
Request the Sitedish to CSV-export connector and get access. You hear from us within 24 hours.
- 02
We agree what should travel
Together we settle what should travel out of Sitedish. A task list or table wants to know where something belongs, and only stays usable with a fixed layout.
- 03
Test and switch on
You check the connector on a few test records before anything becomes final, then it runs by itself.
What you need
- A store you administer, with API access from its admin.
- An account with edit rights, and the list or project it should land in.
Where it runs
Inside your Shopify admin, as an app. You sign in through Shopify, no separate account.
Request this connector: tell us what you need and we reply within 24 hours.
Common questions
Can you connect Sitedish to CSV-export?
Yes. Schakel connects through the official APIs of Sitedish and CSV-export, so you install nothing on your own server and nothing travels outside those two parties.
Which CSV-export project or list do the tasks land in?
The project or list you choose. That keeps everything in one place rather than scattered, and follow-up does not depend on someone remembering.
Can I decide what goes into the CSV-export task or row?
Yes. When setting it up you pick which details from Sitedish come along, so a task or row in CSV-export has just enough context.
What happens on a refund or partial cancellation in Sitedish?
It comes across, so CSV-export matches what was actually settled and you correct nothing by hand.
What does connecting Sitedish and CSV-export cost?
You start free and only pay once the connector is really running. After that the same tiers apply as for any other connector, based on how much runs through it each month.
How often does Sitedish sync with CSV-export?
That depends on your tier: hourly on the free tier up to real time on the unlimited tier. You can always start a sync yourself as well.
What if Sitedish or CSV-export is briefly unavailable?
Nothing gets lost. Schakel retries later and the log shows exactly what happened, so at most you notice something coming through a little later.
How do I connect Sitedish to CSV-export?
You give Schakel access to Sitedish and CSV-export once and pick what should travel. We set it up together with you, so no technical knowledge is needed, and after that it runs by itself.
Connect a different pair
Sitedish and CSV-export is one of many. Pick two systems and see what travels between them.
Missing something you need?
Tell us what Sitedish and CSV-export should do for you. If it is not in here yet, that is usually because nobody has asked. We build on request and we reply within 24 hours.