One limitation of using stripe as a backend, is that many online sellers end up using multiple marketplaces. I sell via my web store (stripe backed), via tindie, and via reverb.com. I started building an admin app to handle generating shipping labels and tracking order status. My initial version used stripe metadata to store all this, and it worked great - but once i started selling elsewhere, i had to use a traditional db backend to store data associated with those orders.
That's an interesting insight, and I'd like to learn more about it.
Off the top of my head, have you considered using the Stripe API directly in those other places? i.e. Stripe as the source of truth, with data being fetched to those other places as REST calls for example?
I imagine that linking those "other" orders with products might be a bit tricky, though
Oh... I hadn't though of that. I guess you're suggesting maybe tracking orders in stripe by creating new orders to mirror the ones made outside of stripe? I would have guessed that stripe's api wouldn't have room for that - but that might be short shortsightedness on my part. I may have to look into that next time I touch the admin app.
