1. Current status
Live snapshot of Shelfdoc and the upstream services we depend on. The source of truth for whether something on our side is broken right now.
Shelfdoc app
Operational
Web app, dashboard, and seller actions are all responsive.
Amazon integration
Operational
Inventory, Subscribe & Save, Disposal Requests, and Catalog reachable from our region.
Background sync
Operational
Velocity refresh, Subscribe & Save sync, expiration audit, and alert delivery all running on schedule.
Updated by hand the moment we know about an issue. We'll publish a measured uptime number once we have ≥ 90 days of post-launch data — until then a precise figure would be guesswork.
2. Dependencies
Shelfdoc sits on top of Amazon's official seller integration. When Amazon's side is degraded, we're degraded too. When we're degraded and Amazon isn't, that's on us.
Amazon services
Inventory reports, Subscribe & Save data, pricing updates, FBA→FBM flips, Disposal Requests, Catalog.
Outages cascade into stale dashboards and delayed Disposal Request submissions.
Seller Central system status3. Reliability model
Shelfdoc assumes Amazon owns the inventory, not us. Our job is to observe, alert, and file the right Disposal Requests at the right time. The product is robust to short outages because:
- Mapping data lives in our database. A multi-hour Amazon outage doesn't lose your expiration-date assignments.
- Audit and disposal queues are safe to retry. The dashboard shows what should be done; the background sync prevents the same disposal from being filed twice.
- When Amazon rejects a Disposal Request, we record the verbatim error and show a Retry button. We don't silently re-submit.
- Sample-data demos render without an Amazon connection — onboarding still works during an upstream outage.
4. Planned maintenance
Small changes deploy daily during US East business hours. Most deploys are zero-downtime. Maintenance requiring a read-only window is announced 24 hours in advance via this page and email.
5. Recent incidents
No public incidents on record.
When something breaks, a short post-mortem lands here — what broke, how it was detected, what changed. Entries stay permanently.
6. Report an outage
If something looks wrong but this page shows green, we probably don't know yet. Email support@shelfdoc.com with:
- What you were trying to do.
- What happened (verbatim error, or “nothing happened”).
- The URL or page name.
- Approximate time (US Eastern is fine).
Subscribers typically get a response within one business day — most same-day. If you need a fast turnaround on the audit-trail export, mention urgency in the subject line.
7. Service-level posture
Shelfdoc doesn't publish a formal SLA. We're post-launch but pre-scale, and a hard 99.9% number we can't verify externally would mislead more than it would help. What we do when something goes wrong:
Disposal Request integrity
If a Shelfdoc bug submits an incorrect Disposal Request (wrong MSKU, quantity, or destination) and Amazon executes it, we will help you file the Amazon reimbursement claim and fix the bug at source.
Data accuracy
Mapping data lost to a Shelfdoc bug is restored from backups where recoverable. We work with you to reconstruct any record we can from Amazon-side sources and the Audit Log.
Outages we cause
Outages over four continuous hours that block disposal submissions are posted here and via in-app banners as soon as we detect them. We communicate transparently while we restore service.
Outages Amazon causes
Amazon-side outages cascade into Shelfdoc by design. We post them here and via in-app banners as soon as we detect them. Resolution depends on Amazon.
Subscription fees are non-refundable. Shelfdoc does not offer refunds, credits, prorated refunds, satisfaction guarantees, or fee absorption. Fees already paid for a billing period are final except where required by law. There is no termination fee. See Terms of Service § 3 for the formal language.