HMAC-SHA256 signed
Every delivery is signed with a shared secret and timestamped to support replay protection.
Reach every Neto merchant without building a Neto integration.
Synckony delivers near-real-time webhook events from Neto stores to your endpoint with the same integration posture as your Shopify and BigCommerce models. Zero Neto-specific polling code.
The platform gap
Neto’s native coverage vs. the rest.
Neto currently provides webhooks only for order status changes. Every other resource — products, customers, inventory, categories, payments, etc. — has no webhook support. This forces third-party integrations to poll the Neto API independently, creating stale data and rate-limit contention.
| Capability | Shopify | BigCommerce | Neto native | Neto + Synckony |
|---|---|---|---|---|
| Order webhooks | Full | Full | Status changes only | Full |
| Product webhooks | Full | Full | No | Full |
| Customer webhooks | Full | Full | No | Full |
| Inventory webhooks | Full | Full | No | Full |
| Content webhooks | Full | Full | No | Full |
| Cart webhooks | Full | Full | No | Full |
| Payment webhooks | Full | Full | No | Full |
| Deletion detection | Full | Full | No | Full |
Delivery reliability
Production-grade webhook delivery.
72-hour retry window
Exponential backoff protects transient failures and prevents silent event loss.
Sequence numbers
Monotonic sequence tracking helps consumers detect gaps and process events correctly.
Idempotency keys
Deterministic event identifiers make retry handling and deduplication safe.
Circuit breaker
Failing endpoints are isolated before they can create retry storms or runaway cost.
Batch & digest mode
Reduce HTTP overhead for high-frequency resources without losing operational visibility.
Integration options
Two ways to connect.
Catalogue integration
Synckony builds and maintains the integration so your app appears in the catalogue and merchants can activate it with minimal friction.
You maintain
A webhook receiver endpoint and the app-side business logic.
Synckony maintains
Polling, change detection, event formatting, delivery, retries, and merchant onboarding.
Custom webhook subscription
Register your own webhook endpoints programmatically and consume raw event data for the stores you serve.
You maintain
Webhook receiver logic, event processing, and data mapping on your side.
Synckony maintains
Polling, change detection, delivery guarantees, and retry orchestration.
Pricing
$1.16 per 10,000 credits. No flat fee.
Compare this to weeks of senior backend development plus ongoing hosting, support, and operational maintenance for your own Neto polling infrastructure. Use the Credits Planner in our pricing page to estimate monthly credit usage from your products, orders, and customers.
| Volume | Approx. monthly cost | Per store |
|---|---|---|
| 10 merchant stores | ~$38.28 | $3.83 |
| 50 merchant stores | ~$191.40 | $3.83 |
| 100 merchant stores | ~$382.80 | $3.83 |
| 500 merchant stores | ~$1,914.00 | $3.83 |
Based on roughly 33,000 events per store per month with one aggregate bill across stores.
Already on Neto?
Migrate incrementally. Zero risk.
Keep your existing Neto polling active, run Synckony in parallel, compare results, and retire legacy polling only when you are comfortable.
01
Parallel run
Register Synckony webhooks alongside your existing polling and validate event parity.
02
Shift primary
Switch your main data source to Synckony while retaining polling as a temporary fallback.
03
Retire polling
Decommission bespoke Neto polling infrastructure and align architecture across platforms.
Ready to reach Neto merchants?
Book a call to discuss integration requirements and the right partner path for your app.