We run a business first. Then we build its systems.
Xinosys is the team behind Patisco. What we do is business development plus software development: backed by a trading company exporting since 1983, we first get your business right with you, then build its systems — and every system we build runs in our own business first.
Patisco 貿商道
Moves everything an exporter exchanges with customers and suppliers — product data, quotes, negotiation, orders, documents, shipping — out of email and Excel into one system. Now in its fourth generation.
Read the case →- 01Point Asia’s team used to be fully occupied by five large European customers. With Patisco, the same team now also serves 500+ smaller buyers.
- 02Selected for DEMO Fall 2011 in the US and Asia Red Herring 100; angel round from AppWorks in 2012; paid service since 2013.
- 03Businesses in 43 countries served and more than US$4M transacted on the platform; featured as a Taipei City digital transformation case in 2025.
- Live, in active development
Most teams write what you ask for. We first help you get the business right.
A typical contractor takes your requirements and starts coding; if the result doesn’t work, that’s your problem. We are different. We have done business in trade, distribution and logistics for forty years, visited thousands of shops and worked with hundreds of factories. We bring that business-development experience to the table: first understand how you make money, why your customers buy and where value leaks — then decide what the system should and shouldn’t do.
Five traders chasing one order
An importer needing 100 units would ask five traders at once; the factory thought 500 were coming, everyone slashed prices, and the buyer ended up with the cheapest, least reliable parts. Point Asia did the opposite: work long-term with a few good factories and concentrate.
→So Patisco is an invitation-only network: inquiries go only to the right partners and every customer sees its own prices — no shouting on an open market.
One shop, 500 wheelsets in a winter
A high-end US road shop ordered 500 front and 500 rear hubs at our first meeting. They swapped premium factory wheelsets for hand-built ones under their own warranty, resold the originals at full price, and kept part-time staff building wheels through the snowy winter.
→Give customers the right materials and their own method emerges. We shape systems around how a client makes money, not around a feature checklist.
A stem three times the price, sold out
A major brand made a full set of fitting stems, and shops wouldn’t order: bikes over US$3,000 are built light, and 6061 aluminium was too heavy. We had a factory switch to lightweight 7005 alloy — three times the cost — and it sold out on launch.
→In discovery, our most common question isn’t “what features do you want?” but “why aren’t customers buying?” The answer is rarely in the spec.
One 5% rule changed how shops ordered
Orders over US$2,000 earned a 5% rebate — exactly the PayPal fee handed back to the shop. Soon everyone ordered above US$2,000.
→Good commercial rules change customer behaviour. We build pricing, rebates and terms straight into the system’s pricing engine instead of relying on salespeople to remember.
Three carriers before freight added up
One carrier’s pricing was chaos; the next gave discounts but miscalculated until our cost baseline drifted; we settled on UPS for its digital focus. Plugging its API into Patisco was a disaster at first — it took years to get the numbers right.
→Integration isn’t done when it connects; it’s done when the numbers reconcile. Most of the pitfalls you would hit, we already have.
Before launch, 40 shops tried it first
When Patisco’s first version was ready in 2012, our German partner invited 30–40 European shops and small distributors to a closed session at Eurobike to test one thing: is buying on it easy?
→That’s why every phase we deliver is accepted by real users — not declared done by the engineers.
Business is a series of conversations
The first line we wrote in 2011 still holds. Quote, negotiation, order, shipment: each step is two parties confirming the same thing. A system’s job is to turn those conversations into structured records, not leave them scattered across inboxes and spreadsheets.
With a system behind you, complexity is fine
Point Asia has traded bicycle parts, GPS units, RFID, industrial computers — even clothing to Japan. What we learned: business is always messy. The problem is not the mess, it is whether a system is there to catch it.
We use it before you do
Patisco, PAXIS and Pedaling Forward all ran in Point Asia’s real business first. We are the first to know which button nobody presses and which document gets typed twice.
AI inside the workflow, decisions with people
We use AI to read documents, business cards and manuals into data, and to build faster. But a person always confirms before anything is written to the system.
PAXIS
Point Asia’s in-house inventory system, sitting behind Patisco: Patisco handles dealings with the outside world, PAXIS handles the moment goods move in or out of the warehouse.
Read the case →Pedaling Forward
A channel program, launched in 2013, connecting Taiwanese bicycle-parts makers directly with independent bike shops overseas. Relaunched in 2026 as a multilingual trade media site.
Read the case →AGILE GDS
A combined warehousing, global dispatch and supply-chain finance service for bicycle brands producing in Taiwan. Stock sits in one warehouse in Taichung and ships worldwide from there, so brands need no overseas warehouse — with Patisco as the single source of truth for the whole flow.
Read the case →A senior team plus AI, delivering what a whole software house does.
Our development team spans project management, back end and front end, and every engineer has more than twenty years of coding behind them. From the database to the phone screen, from payments and logistics to AI, we build the whole line ourselves — nothing subcontracted. AI makes us even stronger: senior engineers own the architecture, judgment and review; AI brings the speed and breadth.
See what we can build →- 20+
- years of coding, per engineer
- 16
- back-end services we run behind Patisco
- 12min
- downtime to jump the production database two major versions
- 1day
- for this website, from old files to live
Custom systems
Orders, inventory, production, booking, membership — one team from first interview to ongoing support.
Patisco onboarding and custom modules
Exporters can use Patisco as is; companies with special workflows get a module built on top, not a system from scratch.
Process and service design
Still figuring out how the business should work? We map the process, responsibilities and data flow first, then decide whether code is needed.
Websites, social and digital marketing
Chinese, English and Japanese sites and blogs, scheduled social posting, ads and analytics — with AI-assisted drafting and translation, published after your team reviews.
Tick a few boxes. We’ll come to talk with the estimate in hand.
No requirements document, no phone calls or emails. Tick the features you need in the estimator and send it — it goes straight into our system, and we’ll come back within one business day with the estimate to set up a conversation.