E-Commerce · head to head
BackToMe vs DynamoDB

BackToMe
E-Commerce
Right-of-withdrawal handling for European e-commerce
- From
- €25/month
- Free plan
- No

DynamoDB
Databases
AWS-only managed key-value and document database with fixed per-partition throughput limits and no ad hoc queries.
- From
- Free
- Free plan
- Yes
The short version
- DynamoDB has a free plan, then $0.625/mo; BackToMe starts at €25/mo.
- Only BackToMe lists floating withdrawal button; only DynamoDB lists managed and serverless.
- Where BackToMe falls short: the scope is European consumer law. A merchant selling outside the EU has no use for it.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which BackToMe and DynamoDB actually diverge.
Not yet recorded: founded for BackToMe.
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in BackToMe
- Floating withdrawal button
- Automatic acknowledgement
- Sealed archiving
- Withdrawal dashboard
- One-click proof export
- Multi-store from one account
Only in DynamoDB
- Managed and serverless
- Predictable latency
- On-demand or provisioned capacity
- Global secondary indexes
- Transactions
- DynamoDB Streams
- Global tables
- Point-in-time recovery
What people use each for
The jobs each tool is most often brought in to do.
BackToMe
- Meeting EU Directive 2023/2673 withdrawal obligationsnot DynamoDB
- Producing dated proof of a cancellation in a customer disputenot DynamoDB
- Handling withdrawal requests across several EU languagesnot DynamoDB
- Running one withdrawal process across multiple storefrontsnot DynamoDB
- Passing a consumer-protection audit with exportable recordsnot DynamoDB
DynamoDB
- High-volume keyed workloads such as sessions, shopping carts, device state or user profiles where the access pattern is fixed and knownnot BackToMe
- Traffic that spikes unpredictably, where on-demand capacity absorbs a burst without a capacity-planning exercisenot BackToMe
- Serverless applications on Lambda, where an HTTP-based datastore avoids the connection pooling problem relational databases havenot BackToMe
- Event or telemetry ingestion where writes vastly outnumber reads and each record is retrieved by a known identifiernot BackToMe
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
BackToMe
- The scope is European consumer law. A merchant selling outside the EU has no use for it
- The site and dashboard are French. The customer-facing button covers 24 EU languages, but the merchant side is not multilingual
- One price, one feature set. There is no tier for a shop that wants only the archive or only the button
- It runs as an injected script on the storefront, so a shop with a strict content security policy has an extra step before the button will render
- A young French vendor with no independent review coverage, so there is nothing outside the vendor's own material to corroborate the archive's evidentiary weight
DynamoDB
- Access patterns must be designed into the key schema before launch; a query nobody anticipated needs a new global secondary index, which is a full extra copy of the projected attributes billed as storage and as writes, or an offline migration
- Global secondary indexes are eventually consistent and cannot be read strongly, so a read-after-write against an index can legitimately miss the item that was just written, and application code must be written to tolerate that
- Per-partition throughput is capped at roughly 3,000 read and 1,000 write units, so a hot key throttles even when the table has spare capacity overall, and the only real fix is changing the key design to spread the load
- Items are limited to 400 KB and query results paginate at 1 MB, so large or list-shaped data has to be split, offloaded to S3 with a pointer, or read through pagination loops that complicate every consumer
- It runs only on AWS and the API is proprietary rather than a standard, so moving the data layer means rewriting it; ScyllaDB's Alternator is the only meaningfully compatible target and it brings a much smaller ecosystem
Pricing, plan by plan
BackToMe
€25/month- Monthly€25/mo
- Per active store, excluding VAT
- Unlimited withdrawal requests
- 24 EU languages
- Annual€250/yr
- Per store, excluding VAT
- Two months free against the monthly rate
- Everything in the monthly plan
DynamoDB
Free- On-Demand CapacityOn request
- Pay-per-request pricing with automatic scaling
- Read: 0.5 RRU per 4 KB (eventually consistent), 1 RRU per 4 KB (strongly consistent), 2 RRU per 4 KB (transactional)
- Write: 1 WRU per 1 KB
- Provisioned CapacityOn request
- Fixed hourly charges based on reserved capacity
- RCU rate: $0.00013 per hour (Standard)
- WCU rate: $0.00065 per hour (Standard)
- Standard Table Class Storage$0.25/per gb/month
- $0.25 per GB/month after free tier
- First 25 GB free per month (free tier)
- Standard-Infrequent Access Table Class$0.1/per gb/month
- $0.10 per GB/month
Which should you pick?
Choose BackToMe if
- You need floating withdrawal button.
- You also want automatic acknowledgement.
Choose DynamoDB if
- You need managed and serverless.
- You want to start without paying.
- You work on AWS.
- You also want predictable latency.
Questions people ask
- Is BackToMe or DynamoDB better?
- Neither clearly leads. BackToMe starts at €25/month and DynamoDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BackToMe or DynamoDB?
- DynamoDB has a free tier; the other does not. Paid plans start at €25/month for BackToMe and Free for DynamoDB.
- Does BackToMe or DynamoDB run on more platforms?
- BackToMe runs on Web. DynamoDB runs on AWS.
- Can I use DynamoDB for free?
- Yes. DynamoDB has a free tier, so you can try it without paying. BackToMe starts at €25/month.
- What is BackToMe best used for?
- BackToMe is most often used for meeting eu directive 2023/2673 withdrawal obligations, producing dated proof of a cancellation in a customer dispute, handling withdrawal requests across several eu languages, running one withdrawal process across multiple storefronts. Of those, meeting eu directive 2023/2673 withdrawal obligations and producing dated proof of a cancellation in a customer dispute are not what DynamoDB is typically brought in for.
- What can BackToMe do that DynamoDB cannot?
- BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. DynamoDB covers Managed and serverless, Predictable latency, On-demand or provisioned capacity, Global secondary indexes.
Answered from the vendors’ own pages
BackToMe: What does BackToMe cost?
25 euros excluding VAT per month per active store, or 250 euros excluding VAT per year, which works out at two months free. The price does not change with the number of withdrawal requests.
SourceDynamoDB: On-demand or provisioned capacity?
On-demand suits unpredictable or spiky traffic and removes capacity planning. Provisioned with autoscaling is considerably cheaper for steady high-volume workloads. Tables can be switched between them, though not arbitrarily often.
BackToMe: Which regulation does it address?
EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.
SourceDynamoDB: Can I run DynamoDB outside AWS?
No. DynamoDB Local exists for development and testing only. For a production-compatible alternative elsewhere, ScyllaDB's Alternator implements the DynamoDB API, but it is a different system with a different ecosystem.
BackToMe: Is there a free trial?
Seven days. A card is required to start it but nothing is charged upfront, and cancelling before day seven costs nothing. There is also a 30-day money-back guarantee.
SourceDynamoDB: Can I run ad hoc queries or analytics?
Not on the table itself. Scans are slow and expensive at scale. The usual pattern is to export to S3 or stream changes out and query them in Athena, Redshift or another analytical engine.
BackToMe: Are staging and development stores billed?
No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.
SourceDynamoDB: Is single-table design necessary?
It is the pattern that gets the most from DynamoDB when access patterns are well known, because it lets related items be retrieved in one query. It also makes the model harder to evolve, so many teams reasonably choose multiple simpler tables and accept extra requests.
BackToMe: What happens to the archive if I cancel?
Cancellation is available at any time with no commitment, premium access runs to the end of the paid period, and the account stays open with archived withdrawals and proofs accessible indefinitely. Reactivation is self-service.
SourceDynamoDB: What are the real limits I should design around?
400 KB per item, 1 MB per query or scan page, 100 items per transaction, roughly 3,000 read and 1,000 write units per partition, and eventual consistency on global secondary indexes.
BackToMe: Which e-commerce platforms does it support?
Shopify, WordPress, WooCommerce, PrestaShop, Wix, Webflow, WiziShop and Squarespace, plus custom builds through a single line of script. The vendor puts installation at five minutes on any platform.
SourceRelated pages
Other head to heads
- BackToMe vs Temu
- BackToMe vs Amazon Shopping
- BackToMe vs Mailchimp
- BackToMe vs Shein
- BackToMe vs CJ Dropshipping
- BackToMe vs Memberful
- BackToMe vs Wish
- BackToMe vs Zendrop
- BackToMe vs Heartland Retail
- BackToMe vs Vinted
- BackToMe vs Mollie
- BackToMe vs TikTok Shop
- BackToMe vs SamCart
- BackToMe vs Sellfy
- BackToMe vs Shopware
- BackToMe vs Spree Commerce
- BackToMe vs Swell Commerce
- BackToMe vs Toast
- BackToMe vs MongoDB
- BackToMe vs Elasticsearch
- BackToMe vs Cassandra
- BackToMe vs BigQuery
- BackToMe vs FaunaDB
- BackToMe vs Memcached
- BackToMe vs ScyllaDB
- BackToMe vs PlanetScale
- BackToMe vs Couchbase
- BackToMe vs DataGrip
- BackToMe vs Firebase Realtime Database
- BackToMe vs Microsoft SQL Server
- BackToMe vs QuestDB
- BackToMe vs Vitess
- BackToMe vs Aiven
- BackToMe vs CouchDB
- BackToMe vs Google Cloud SQL
- BackToMe vs CosmosDB
- DynamoDB vs Temu
- DynamoDB vs Amazon Shopping
- DynamoDB vs Mailchimp
- DynamoDB vs Shein
- DynamoDB vs CJ Dropshipping
- DynamoDB vs Memberful
- DynamoDB vs Wish
- DynamoDB vs Zendrop
- DynamoDB vs Heartland Retail
- DynamoDB vs Vinted
- DynamoDB vs Mollie
- DynamoDB vs TikTok Shop
- DynamoDB vs SamCart
- DynamoDB vs Sellfy
- DynamoDB vs Shopware
- DynamoDB vs Spree Commerce
- DynamoDB vs Swell Commerce
- DynamoDB vs Toast
- DynamoDB vs MongoDB
- DynamoDB vs Elasticsearch
- DynamoDB vs Cassandra
- DynamoDB vs BigQuery
- DynamoDB vs FaunaDB
- DynamoDB vs Memcached
- DynamoDB vs ScyllaDB
- DynamoDB vs PlanetScale
- DynamoDB vs Couchbase
- DynamoDB vs DataGrip
- DynamoDB vs Firebase Realtime Database
- DynamoDB vs Microsoft SQL Server
- DynamoDB vs QuestDB
- DynamoDB vs Vitess
- DynamoDB vs Aiven
- DynamoDB vs CouchDB
- DynamoDB vs Google Cloud SQL
- DynamoDB vs CosmosDB
