ADOBE

COMMERCE

Carefully, because it is where most of the recoverable revenue hides. We treat each method as a distinct payment path with its own routing, reconciliation and refund handling, rather than installing an extension and trusting the defaults. The failure modes we see most often are callback and webhook misconfiguration, where the processor authorizes successfully but the order never reaches Magento or arrives in the wrong state, and mismatches between what the gateway settled and what the store recorded. We audit the full transaction lifecycle, repair the order state machine, reconcile against settlement files, and instrument the failure paths so problems surface before customers report them. Atlanta merchants tend to be unusually fluent about payments, given how much of the industry sits in this metro, and the conversations are sharper for it.

Mostly MARTA. Fulton and DeKalb both fund the transit authority through a 1% levy inside their county rates, while Cobb, Gwinnett and Cherokee sit outside the service area and do not, which is why suburban metro rates run lower than the city. Layered on top are SPLOST, E-SPLOST and T-SPLOST special district taxes, funding education, transportation and infrastructure county by county. The part worth planning around is that these expire on defined terms and lapse automatically unless voters renew them, so a rate you configured correctly can quietly become wrong without anyone touching your store. That is the argument for a live tax engine over a maintained rate table.

No, and this is worth getting right because it is widely misreported. Senate Bill 111 was introduced as the Georgia Consumer Privacy Protection Act, but the House replaced its entire text with unrelated rural hospital tax credit amendments before it passed. The version signed in May 2026 has nothing to do with consumer privacy. Legislative trackers still display the original title, which is why several sources describe a Georgia privacy law taking effect. Georgia has not enacted one. Your real obligations come from wherever your customers live: twenty states now have comprehensive statutes, and twelve require you to honor the Global Privacy Control signal, which Firefox and Brave send by default. We build the signal handling, consent capture and subject request workflows to match, and encrypt personal records at database level through PII Shield. Have counsel confirm which states apply to you.

Courts have generally treated commercial websites as places of public accommodation under Title III, and WCAG 2.1 Level AA is the benchmark both sides work to. Federal website accessibility filings reached 3,117 in 2025, up 27% year on year, with e-commerce absorbing the large majority. Overlay widgets are not a remedy. The FTC required accessiBe to pay $1 million in 2025 over claims its automated tool could make any site WCAG-compliant, and roughly a quarter of sites sued already had a widget running. We remediate in the code across catalog, search, cart and checkout, then hold conformance as content changes. Documented, commercially reasonable remediation has helped defendants get cases dismissed, so the work carries defensive value alongside the commercial case.

Three phases, tested repeatedly: discovery and audit, then replatform and migrate, then hypercare and optimization. Before anything moves we clean and validate your data, so stale or duplicated records do not follow you onto the new platform. Catalogs, customers, orders and SEO redirects transfer through migration accelerators proven across 50+ projects, with old and new running in parallel on delta syncing until traffic shifts, rollback ready. On search visibility, we map every URL, implement 301 redirects, carry metadata and structured data across intact, and re-establish Core Web Vitals baselines before cutover. Most migrations we run hold rankings or improve them, because the replacement store is quicker and easier to crawl than what it replaced.

It depends which side of a county line they live on, which catches a surprising number of stores out. The City of Atlanta rate is 8.9%, made up of 4% Georgia state tax, 3% Fulton County, 1.5% City of Atlanta and 0.4% for transportation. But Atlanta straddles Fulton and DeKalb counties, and the DeKalb portions of the city sit at 8.0% rather than 8.9%. Two customers with the same city on their address can owe different amounts. Georgia is destination-based, so the rate follows the delivery address rather than your warehouse, and a blanket "Atlanta rate" configured in Magento will be wrong for part of your own city. We integrate Avalara, Vertex or TaxJar for address-level resolution rather than relying on ZIP mapping. Confirm your position with your tax adviser.

The revenue test is settled: $100,000 in gross retail sales into Georgia triggers economic nexus, measured on the current or previous calendar year. The transaction-count test is where you should not take anyone's word, including ours. Georgia has historically applied a $100,000 or 200-transaction standard, but at least one source reports the 200-transaction threshold was removed effective January 2026, while several others published later still describe it as active. Sources also disagree on whether marketplace sales count toward your own threshold. Both points are worth a direct answer from the Department of Revenue or your adviser rather than a guess from any agency page. On digital products, items conveying permanent rights such as e-books, music and downloads are taxable, while SaaS and custom software are not.

The platform supports PCI-DSS through tokenization and hosted payment fields, but Requirements 6.4.3 and 11.6.1 became mandatory in March 2025 and reach further than most merchants realize. Every script running on a payment page needs authorization, written justification and integrity verification, plus tamper detection covering scripts and HTTP headers. A live Magento checkout typically carries tag managers, analytics, chat and review scripts, and each one falls in scope. These requirements exist because of Magecart, an attack family named for Magento shopping carts. We inventory what runs on your payment pages, document why it is there, and put change detection in place.

Yes. REST and GraphQL APIs, webhooks and message queues connect Adobe Commerce to major ERP platforms including NetSuite, SAP and Microsoft Dynamics, to CRM systems such as Salesforce and HubSpot, and to PIM tools. We shorten that work with OmniFlux, our reusable integration framework, which supplies a standardized connector architecture handling event-driven synchronization, data mapping, authentication, retries and detailed logging, keeping product, order, inventory and customer records aligned even under heavy transaction volume.

Scope decides it, but three to six months covers most builds and migrations. A tightly defined smaller project can be trading inside six to eight weeks. Enterprise work involving deep catalogs, several integrations, tax automation and ERP or PIM systems can run to 10 or 12 months. We fix the timeline after a two-week discovery sprint and deliver in two-week sprints with full visibility throughout. Where gateway certification is involved, start that process at kickoff, since it frequently sets the launch date rather than the build does.