What was the problem?
A tire and wheel shop in New Jersey is launching an online store on Shopify. Nobody hand-enters four thousand tire SKUs, so the catalog has to come from the distributor: products, sizes, pricing, stock levels, images. The distributor’s sales rep came back with two options from their IT team. An API, or FTP and sFTP. The shop owner, reasonably, asked us what any of that meant.
Why not the API?
An API is a phone that only answers when called. It gives real-time answers, “what is the stock on this SKU right now,” but nothing happens unless code on our side requests it, transforms it, and pushes it into Shopify. That code has to handle authentication, scheduling, errors, and monitoring, and it has to keep doing that forever, on a client store, with someone responsible when it breaks at two in the morning. For a curated tire store, real time buys nothing: tire prices do not move hourly, and stock accurate to within a day is fine at this volume. The API becomes the right answer only if the shop ever needs live stock checks at checkout. That is not launch scope.
Why the file drop?
An sFTP feed inverts the whole thing. The distributor’s system generates a file on a schedule and pushes it to an address we give them. An off-the-shelf Shopify import app pulls that file on its own schedule, applies a column mapping we set up once, and syncs products, prices, and inventory. Zero custom code between the two. Nothing to babysit. When the distributor updates the catalog, the store updates itself the next morning. The entire integration is a folder and a scheduled job.
Why did the $4 server win?
The distributor needed an sFTP address to push to, so something had to be listening on that protocol somewhere. The managed services built for this start around $50 a month, which is silly money for catching one CSV a night. The cheap European storage box we tried first demanded a photo of the owner’s driver’s license for a $4 rental, which is not a trade any small business should make. So we rented a $4 virtual server from a US host, ran a short setup script that creates a locked-down login for the distributor, one that can only drop files into one folder and do nothing else, and handed over the credentials. An afternoon, most of it spent on the two dead ends.
What does custom software mean for a small business?
This. Not an app with a login and a dashboard. The right piece of plumbing, chosen so that the business owner never has to think about it again. The shop owner in this story now has a catalog that maintains itself, a store that reflects the distributor’s stock, and a monthly infrastructure bill smaller than a car wash. Most of the custom software work Atlas does looks like this: connecting two systems that were never designed to talk, with as little new code as possible, so the connection outlives everyone’s attention span.
Questions people ask
Is sFTP secure enough for business data?
Yes. sFTP is encrypted file transfer over SSH, the same protocol that secures server administration worldwide. The login we create can only write to one folder.
When would the API be the right choice?
When the store needs live stock at checkout or automatic order routing back to the distributor. Neither is a launch requirement for a curated store.
What does the ongoing maintenance look like?
Almost none. The server patches itself, the import app runs on schedule, and the distributor pushes the file. The first time anyone touches it is if the distributor changes their file format.