This page is reference material for Rocon Software Review. Longer pieces that do not fit the review format.
Details
What gets covered here
Migration post-mortems, integration behaviour that only shows up after month two, and pricing arithmetic that the vendor’s own comparison table leaves out. Longer than a review, shorter than a book.
Where a piece touches a published standard, the standard is linked rather than paraphrased: for transport questions that means documents like RFC 3550, and for storefront behaviour the vendor’s API reference.
Reference material
Where a review discusses a published standard or a vendor API, we work from the primary document rather than a secondary summary. For storefront data that means the vendor’s own Admin API reference; for real-time transport questions it means the governing specification, for example RFC 3550. If a document we cite has been superseded, tell us and we will correct the link.
Pieces are written after the fact, from notes taken during the work, which is why they contain the parts that went wrong rather than a clean narrative.
How to read this page
“If a claim about a connector cannot be checked against the vendor’s own documentation, it belongs in a blog post, not in a review.” — our internal editing rule.
Everything on this page is written to be checkable. Where we cite a vendor’s API or a published standard, the link points at the primary document rather than a summary, so a reader can verify the claim without taking our word for it.
What is on this page
This page is reference material for Rocon Software Review: roughly 300 words of context, 2 primary-source links, and the specific limits of what we can tell you here.
Scope
The scope is deliberately narrow. It covers what the page title says and nothing adjacent, because a reference page that sprawls is a page nobody finishes. Three constraints apply: the material is checked at publication, re-checked quarterly, and corrected in place with a dated note when it goes stale.
How it is maintained
Two people maintain this page. Reviews are re-checked every 90 days against the vendor’s published pricing, and every correction is dated in the page body rather than silently applied.
At a glance
- Published since 2021
- Two editors, both operators of small businesses
- Reviews re-checked every 90 days
- Corrections dated in the page body
Terms used on this page
A connector is a service that moves records between two systems on a schedule or on an event. A webhook is an HTTP callback that a system sends when something changes, rather than waiting to be polled. An item fulfilment is the record that says a physical shipment left the warehouse, and it is a different object from the sales order it belongs to.
- Sales order — the record of what a customer bought
- Item fulfilment — the record of what actually shipped
- Inventory level — available quantity at a specific location
- Location — a warehouse, a store, or a virtual bucket
- Matrix item — a product with variants inherited from an option schema
- Upsert — create if absent, update if present
- Idempotency key — a value that stops a retry from creating a duplicate
- Reconciliation — the manual or scripted comparison of two ledgers
- Backfill — replaying historical records into a new system
- Cutover — the moment the new system becomes authoritative
- Drift — the state where two systems disagree without either raising an error
- Circuit breaker — a mechanism that stops retrying a failing integration