How to Serve Legal Papers on Amazon.com

The most common procedural error in Amazon litigation does not happen at the courthouse — it happens at the caption. “Amazon” is not a legal entity. A summons captioned “Amazon,” “Amazon.com,” or “Amazon Corporation” names nothing that appears on any Secretary of State’s corporate registry in any state. Amazon.com, Inc. — the Delaware-incorporated, Seattle-based publicly traded parent company — is one entity among more than forty registered Amazon subsidiaries, each incorporated separately, each with its own registered agent, and each carrying distinct liability for the specific business function it performs. Filing against the wrong entity, or filing against a name that corresponds to no entity at all, produces a motion to dismiss for improper service that Amazon’s national litigation counsel files routinely and wins regularly.

The major litigation-relevant entities are: Amazon.com, Inc. (the publicly traded Delaware parent, NASDAQ: AMZN); Amazon.com Services LLC (the marketplace operating entity — the correct defendant in marketplace product liability cases following the California Court of Appeal’s 2020 ruling in Bolger v. Amazon.com, LLC); Amazon Web Services, Inc. (the AWS cloud subsidiary with its own terms of service designating Washington state courts for commercial disputes); Amazon Logistics, Inc. (the delivery network entity for DSP driver cases); Whole Foods Market, Inc. (a Texas corporation — not a Washington or Delaware entity — for Whole Foods store incidents); and Ring LLC (smart home device product liability and privacy class actions). Each of these is a separate legal entity. Service on one does not constitute service on any other.

Undisputed Legal has served process on Amazon.com, Inc. and its subsidiaries across multiple jurisdictions. Our GPS-verified affidavits, entity-identification review at intake, and current Corporation Service Company registered agent records eliminate the procedural risk that Amazon’s litigation team is specifically positioned to exploit. Call (800) 774-6922 or place your order below to begin.

Why Amazon Is the Most Difficult Corporation to Serve Correctly

Amazon’s registered subsidiary count exceeds forty entities, and that number does not include the hundreds of third-party delivery service partner companies, marketplace sellers, and Amazon Flex independent contractors who operate under the Amazon brand but are not Amazon entities. Every complaint must name a specific registered entity. A plaintiff’s attorney who writes “Amazon” or “Amazon.com” in the caption without specifying the correct operating subsidiary has filed a defective complaint — and Amazon’s outside counsel will identify and exploit that defect before answering on the merits.

The Bolger ruling changed which entity is the correct defendant in marketplace product liability cases. Before the California Court of Appeal’s August 2020 decision in Bolger v. Amazon.com, LLC (53 Cal.App.5th 431), plaintiffs in marketplace product liability cases often argued — and often lost — that Amazon was not a “seller” liable under California strict products liability because it merely hosted the marketplace. Bolger held that Amazon.com Services LLC is strictly liable as a seller for defective products sold through its marketplace by third-party sellers. The correct entity is Amazon.com Services LLC — not Amazon.com, Inc. — for marketplace product liability claims in California and states adopting similar analysis.

Amazon Web Services presents a separate entity problem for commercial and B2B litigation. AWS disputes — data loss, service outages, contract performance failures, SLA breaches — involve Amazon Web Services, Inc., a Delaware corporation with its own terms of service, its own registered agent, and forum selection clauses designating Washington state courts for commercial disputes. Service on Amazon.com, Inc. in an AWS dispute does not reach Amazon Web Services, Inc.’s legal team and will not satisfy service requirements for AWS matters.

Delivery service partner cases present a three-layer entity problem. Amazon Logistics, Inc. manages Amazon’s last-mile delivery network and contracts with independently owned DSP companies. DSP companies employ drivers and operate Amazon-branded vans. A delivery driver injured on the job, or a pedestrian struck by an Amazon delivery van, may have claims against the DSP company (as the direct employer), Amazon Logistics, Inc. (as the network manager and general contractor), and potentially Amazon.com, Inc. (as the ultimate enterprise defendant). Each entity is separate, requires independent service, and will mount independent defenses regarding control, employment status, and joint-employer liability. Serving Amazon.com, Inc. alone does not reach Amazon Logistics, Inc.

Amazon’s registered agent is Corporation Service Company (CSC) — not CT Corporation System. These are distinct registered agent organizations with different office locations, different intake procedures, and different processing timelines. A process server who appears at a CT Corporation office with Amazon documents will be turned away. All Amazon entity service routes through Corporation Service Company at CSC’s designated office in the applicable state.

Amazon Corporate Structure — Know Which Entity You Are Serving

Amazon.com, Inc. is the Delaware-incorporated publicly traded parent and holding company. Incorporated in 1994, listed on NASDAQ as AMZN, headquartered at 410 Terry Avenue North, Seattle, Washington 98109. Amazon.com, Inc. is the correct defendant in enterprise-wide corporate governance disputes, securities class actions, FTC and state AG antitrust proceedings (FTC v. Amazon, filed September 2023), and cases where the claim attaches to Amazon’s company-wide policies or executive conduct. Registered agent: Corporation Service Company.

Amazon.com Services LLC is the primary operating entity for Amazon’s retail and marketplace business. This is the entity that contracts with third-party marketplace sellers, operates fulfillment centers, and employs the overwhelming majority of Amazon’s warehouse and logistics workforce in the United States. Post-Bolger, Amazon.com Services LLC is the correct defendant in marketplace product liability cases in California and jurisdictions adopting similar strict liability analysis. It is also the correct entity for FLSA collective actions and state wage-and-hour class actions arising from fulfillment center operations. Registered agent: Corporation Service Company.

Amazon.com Sales, Inc. is a Delaware corporation that handles Amazon’s direct retail sales function in certain transactional contexts. For consumer product disputes involving items sold directly by Amazon (not by a third-party marketplace seller), Amazon.com Sales, Inc. may be the correct seller defendant alongside Amazon.com Services LLC. Registered agent: Corporation Service Company.

Amazon Web Services, Inc. is a Delaware corporation incorporated in May 2006. AWS is the world’s largest cloud computing platform, providing infrastructure, platform, and software services to enterprise, government, and startup customers globally. Disputes arising from AWS service agreements — data loss, service outages, security incidents, SLA breaches, or enterprise contract disputes — name Amazon Web Services, Inc. as the defendant. AWS’s standard customer agreement designates Washington state law and the exclusive jurisdiction of King County, Washington courts (or the Western District of Washington for federal matters). Registered agent: Corporation Service Company.

Amazon Logistics, Inc. is the Amazon subsidiary that operates the Delivery Service Partner (DSP) program and manages Amazon’s last-mile delivery network. For personal injury cases involving delivery drivers, DSP operations, or accidents caused by Amazon-branded delivery vehicles, Amazon Logistics, Inc. is the relevant Amazon entity. Note that DSP companies — the independently owned businesses that employ drivers and operate the vans — are separate entities from Amazon Logistics, Inc. and require their own service. Amazon Logistics, Inc. is not the direct employer of DSP drivers; the legal question of Amazon Logistics’ liability typically turns on control and general contractor theories. Registered agent: Corporation Service Company.

Whole Foods Market, Inc. is a Texas corporation — not a Washington or Delaware entity — headquartered in Austin, Texas. Acquired by Amazon in August 2017, Whole Foods operates as a subsidiary but retains its Texas corporate identity. For premises liability, employment, and consumer claims arising at Whole Foods store locations, the correct defendant is Whole Foods Market, Inc. or a Whole Foods operating subsidiary — not Amazon.com, Inc. Whole Foods Market Services, Inc. is a related entity that provides HR and administrative services. Registered agent for Whole Foods Market, Inc.: Corporation Service Company at the applicable state address. In Texas, Whole Foods’ home jurisdiction, verify the current registered agent with the Texas Secretary of State.

Ring LLC is a Delaware limited liability company acquired by Amazon in February 2018. Ring manufactures smart home security devices — video doorbells, security cameras, alarm systems — and operates the Neighbors public safety platform. Product liability cases involving defective Ring devices, privacy class actions arising from Ring camera data practices, and law enforcement data-sharing litigation name Ring LLC as the defendant. The Ring HQ is in Hawthorne, California. Registered agent: Corporation Service Company.

Audible, Inc. is a Delaware corporation acquired by Amazon in 2008. Audible operates the audiobook and spoken-word content platform. Consumer disputes, content licensing cases, and employment matters at Audible’s Newark, New Jersey campus name Audible, Inc. as the defendant.

Twitch Interactive, Inc. is a Delaware corporation and the operator of the Twitch live streaming platform, acquired by Amazon in 2014. Content moderation, creator monetization, and platform access disputes name Twitch Interactive, Inc. HQ: San Francisco, California.

Zappos.com LLC is the online footwear and apparel retailer acquired by Amazon in 2009, operated from Las Vegas, Nevada. Consumer product, return policy, and employment disputes at Zappos name Zappos.com LLC as the defendant — not Amazon.com, Inc.

Not Amazon: Amazon Flex drivers are independent contractors, not employees of any Amazon entity. DSP company employees are employed by independently owned DSP businesses. Third-party marketplace sellers are separate legal entities with their own registered agents. None of these parties is reachable through service on Amazon.com, Inc. or any Amazon subsidiary.

Our 7-Step Process for Serving Amazon

Our corporate process service protocol for Amazon entities follows a documented seven-step sequence. The entity-identification step is more consequential for Amazon than for virtually any other corporate defendant — we execute it at intake on every order.

Step 1 — Identify the Correct Amazon Entity. We review the complaint caption, the nature of the dispute, and the specific business function involved. Marketplace product liability: Amazon.com Services LLC. AWS dispute: Amazon Web Services, Inc. Delivery driver injury: Amazon Logistics, Inc. (and separately, the DSP company). Whole Foods store: Whole Foods Market, Inc. Ring device: Ring LLC. Enterprise-wide policy or securities: Amazon.com, Inc. Any caption that reads only “Amazon” or “Amazon.com” is flagged to counsel for correction before service proceeds.

Step 2 — Verify Current CSC Registered Agent Address. We confirm Corporation Service Company’s current registered agent address with the applicable Secretary of State on the day of engagement. CSC maintains offices in all fifty states and the District of Columbia. Addresses change. We do not rely on prior orders or databases — we verify fresh on every assignment.

Step 3 — Prepare and Review All Legal Documents. We review the summons, complaint, and all accompanying court orders for completeness before dispatch. Entity name mismatches, missing exhibits, and incomplete summons forms are flagged to counsel before the server leaves the office.

Step 4 — Confirm Jurisdiction and Applicable Service Rules. FRCP Rule 4, state rules of civil procedure, and any MDL case management orders or forum-specific requirements applicable to the Amazon entity named in the complaint are confirmed before service. AWS matters in Washington state courts carry jurisdiction-specific requirements under the AWS Customer Agreement’s forum selection clause.

Step 5 — Execute Service with GPS Verification. Our servers carry GPS-enabled devices that timestamp and geolocate each service attempt at the moment of delivery. In New York City’s five boroughs, our servers hold active DCWP process server licenses as required by local law. Photo documentation supplements GPS data on every corporate delivery. First service attempt is made within 3–7 business days of order placement, subject to any court or counsel-imposed deadline.

Step 6 — Generate GPS-Verified Affidavit of Service. Every completed service produces a GPS-verified affidavit identifying the server, the Amazon entity served, the Corporation Service Company office, the date and time, the precise GPS coordinates, and the method of delivery. The affidavit is formatted to the filing court’s requirements and delivered in final, court-ready form.

Step 7 — Deliver Proof of Service to Counsel. Completed affidavit and all documentation are transmitted to counsel within 24 hours of service completion. Same-day affidavit production is available for emergency filings with advance notice.

Ready to serve Amazon? Call (800) 774-6922 or use the order widget below — we confirm entity, CSC address, and jurisdiction before dispatch.

Where to Serve Legal Papers on Amazon — State by State

Consult an attorney to confirm the correct Amazon entity and registered agent for your specific jurisdiction and claim type. CSC registered agent addresses are subject to change; verify with the applicable Secretary of State before each service attempt.

Washington — Home State and Principal Office. Amazon.com, Inc. is headquartered at 410 Terry Avenue North, Seattle, Washington 98109. Washington is Amazon’s operational home state, the forum designated by AWS commercial contracts, and the primary jurisdiction for corporate governance and employment matters involving Amazon’s Seattle-based workforce. Amazon.com, Inc. is registered as a foreign corporation in Washington state. Registered agent for Washington service: Corporation Service Company, 300 Deschutes Way SW, Suite 208, Tumwater, WA 98501. RCW 23.95.415 governs service on registered agents for entities registered in Washington; delivery to Corporation Service Company at the Tumwater address satisfies service on Amazon.com, Inc. and Amazon.com Services LLC in Washington. AWS commercial contract matters filed in Washington state follow the exclusive forum designation in the AWS Customer Agreement.

Delaware — State of Incorporation and Governance Forum. Amazon.com, Inc. was incorporated in Delaware in 1994. Delaware’s Court of Chancery is the primary forum for Amazon corporate governance disputes, shareholder derivative actions, executive compensation challenges, and fiduciary duty claims. Amazon Web Services, Inc. is also a Delaware corporation (incorporated May 2006). Service on Amazon.com, Inc. and Amazon Web Services, Inc. in Delaware is made upon Corporation Service Company, 251 Little Falls Drive, Wilmington, DE 19808. 8 Del. C. § 321 governs service on domestic and foreign corporations in Delaware; delivery to Corporation Service Company at 251 Little Falls Drive constitutes complete and effective service. For Chancery Court matters, confirm the Court of Chancery’s specific procedural requirements before service.

Virginia — HQ2 and AWS Concentration. Amazon’s second headquarters — HQ2 — opened in Arlington, Virginia in 2023, anchored at 241 18th Street South, Arlington, VA 22202. Multiple Amazon entities now have significant operational presence in Northern Virginia, and Amazon Web Services runs its largest data center campus (us-east-1) in the Northern Virginia corridor. Employment disputes arising from HQ2 operations, AWS-related contract claims filed in Virginia federal courts (Eastern District), and commercial litigation involving Northern Virginia-based Amazon teams may require Virginia service. Registered agent: Corporation Service Company, 100 Shockoe Slip, FL 2, Richmond, VA 23219. Va. Code Ann. § 13.1-766 governs service on foreign corporations in Virginia; delivery to Corporation Service Company at the Richmond address satisfies service on Amazon.com, Inc. and Amazon Web Services, Inc. in Virginia.

California — Bolger Liability, Ring LLC, and Highest Litigation Volume. California generates more Amazon litigation than any other state. The Bolger v. Amazon.com, LLC ruling (2020) established Amazon.com Services LLC’s strict liability as a marketplace seller in California — the correct entity in product liability cases involving third-party marketplace products sold through Amazon in California. Ring LLC is headquartered in Hawthorne, California; product liability and privacy class actions involving Ring devices are frequently filed in Los Angeles or Santa Monica federal courts. California also generates the highest volume of FLSA and state wage-and-hour class actions against Amazon.com Services LLC for fulfillment center workers. Registered agent for Amazon.com, Inc. and Amazon.com Services LLC in California: Corporation Service Company, 2710 Gateway Oaks Drive, Suite 150N, Sacramento, CA 95833. CCP § 416.10 governs service on domestic and foreign corporations; delivery to Corporation Service Company at the Sacramento address satisfies service on Amazon.com, Inc., Amazon.com Services LLC, and Ring LLC in California.

Texas — Fulfillment Hub and Whole Foods Headquarters. Texas hosts one of Amazon’s densest fulfillment center networks, generating significant employment litigation — FLSA collective actions, state wage claims, and workplace injury cases — naming Amazon.com Services LLC. Critically, Whole Foods Market, Inc. is a Texas corporation headquartered in Austin, Texas. Any premises liability, employment, or consumer claim arising at a Whole Foods store location must name Whole Foods Market, Inc. — or its applicable Texas or state-specific operating subsidiary — as the defendant, not Amazon.com, Inc. Registered agent for Amazon entities in Texas: Corporation Service Company, 211 East 7th Street, Suite 620, Austin, TX 78701. Tex. Bus. Orgs. Code § 5.251 governs service on registered agents in Texas; for Whole Foods Market, Inc. (a Texas domestic corporation), confirm its current Texas registered agent with the Texas Secretary of State separately.

New York — Securities, Antitrust, and AWS Enterprise. The Southern District of New York is the primary forum for Amazon securities class actions and for federal antitrust proceedings that parallel the FTC’s September 2023 complaint against Amazon.com, Inc. New York state courts also handle a high volume of commercial disputes involving Amazon Web Services, Inc. enterprise customers and Ring LLC consumer claims. Audible, Inc. — headquartered across the Hudson in Newark, New Jersey — generates employment and consumer disputes that are frequently litigated in New York federal courts. Registered agent in New York: Corporation Service Company, 80 State Street, Albany, NY 12207. CPLR § 311(a)(1) and BCL § 306 govern corporate service in New York; delivery to Corporation Service Company at the Albany address satisfies service on Amazon.com, Inc., Amazon Web Services, Inc., and Ring LLC in New York.

New Jersey — Fulfillment Center Hub, Logistics, and Audible. New Jersey is one of Amazon’s largest fulfillment and logistics state footprints, hosting multiple fulfillment centers, delivery stations, and DSP contractor operations. Employment class actions for New Jersey warehouse workers name Amazon.com Services LLC. DSP driver injury cases arising in the New Jersey corridor name Amazon Logistics, Inc. and the applicable DSP company. Audible, Inc. is headquartered in Newark, New Jersey; employment and workplace disputes at the Newark campus name Audible, Inc. as the employer defendant. Registered agent in New Jersey: Corporation Service Company, 820 Bear Tavern Road, Ewing, NJ 08628. N.J. Ct. R. 4:4-4(a)(6) governs service on corporations through the registered agent; delivery to Corporation Service Company at the Ewing address satisfies service on Amazon.com, Inc., Amazon.com Services LLC, Amazon Logistics, Inc., and Audible, Inc. in New Jersey.

Compliance and Legal Framework for Amazon Service

Bolger v. Amazon and Marketplace Product Liability. The California Court of Appeal’s August 2020 ruling in Bolger v. Amazon.com, LLC (53 Cal.App.5th 431) held that Amazon.com Services LLC is strictly liable as a “seller” under California products liability law for defective products sold by third-party marketplace sellers through Amazon’s platform. The court reasoned that Amazon exercises sufficient control over the marketplace transaction — setting terms, processing payments, providing fulfillment — to be treated as a seller in the distribution chain. Post-Bolger, the correct defendant entity in California marketplace product liability cases is Amazon.com Services LLC. Multiple other states and federal courts have analyzed Bolger’s reasoning in subsequent cases, and the trend toward imposing marketplace liability on Amazon has accelerated in California coordinated proceedings. Consult counsel to determine whether Bolger-type strict liability applies in your filing jurisdiction.

DSP Driver Cases — The Three-Layer Entity Problem. Amazon’s last-mile delivery model creates a three-layer entity structure that directly affects service of process strategy. Amazon Logistics, Inc. contracts with independently owned DSP companies, which in turn employ drivers. In personal injury and FLSA cases involving delivery drivers, plaintiffs may have viable claims against the DSP company (direct employer), Amazon Logistics, Inc. (general contractor and program manager), and in some theories, Amazon.com, Inc. (ultimate enterprise). Courts applying the joint-employer doctrine under FLSA and state law have reached varying conclusions about Amazon Logistics’ status as a co-employer of DSP drivers, depending on the degree of Amazon’s operational control. Each entity in this chain requires independent service. Serving Amazon.com, Inc. alone does not preserve claims against Amazon Logistics, Inc.

AWS Commercial Disputes — Forum and Entity. Amazon Web Services, Inc. governs its commercial relationships through the AWS Customer Agreement, which specifies Washington state law and grants exclusive jurisdiction to courts in King County, Washington (Western District of Washington for federal matters). B2B litigation arising from cloud outages, data loss, SLA breaches, and enterprise contract disputes must: (1) name Amazon Web Services, Inc. as the defendant — not Amazon.com, Inc.; and (2) be filed in the designated Washington forum unless the forum selection clause is successfully challenged. Service on Amazon.com, Inc. in an AWS dispute will not satisfy service on Amazon Web Services, Inc., and Amazon’s legal team will so advise promptly.

Ring Privacy and Data Breach Cases. Amazon Ring class action litigation spans two primary theories: product liability for defective Ring devices (hardware failures, cybersecurity vulnerabilities) and privacy class actions arising from Ring’s law enforcement data-sharing practices. The correct defendant in Ring product liability and privacy cases is Ring LLC. Alexa voice assistant privacy cases — arising from claims about ambient recording and data retention — more frequently name Amazon.com, Inc. or Amazon.com Services LLC as the entity operating the Alexa platform. The BIPA (Illinois Biometric Information Privacy Act) cases involving Ring and Alexa name the entity whose technology collected the biometric data in the relevant jurisdiction.

FTC Antitrust Proceedings. The Federal Trade Commission filed its antitrust complaint against Amazon.com, Inc. in September 2023 (FTC v. Amazon.com, Inc., W.D. Wash.), alleging that Amazon maintains monopoly power through anti-discounting and anti-competitive seller conditions. State attorneys general have filed related actions. These proceedings name Amazon.com, Inc. — the publicly traded parent — as the primary defendant. Commercial parties who are harmed by Amazon’s alleged antitrust conduct and who file private antitrust actions under Sherman Act § 4 (Clayton Act) should name Amazon.com, Inc. and the applicable operating subsidiary (Amazon.com Services LLC for marketplace-related conduct) as defendants.

Fulfillment Center Employment — Amazon.com Services LLC as Operating Employer. FLSA collective actions and state wage-and-hour class actions arising from Amazon fulfillment center operations name Amazon.com Services LLC as the employer entity. Amazon.com, Inc. — the holding company — is typically not the direct employer of warehouse workers. Complaints that name only “Amazon.com, Inc.” in employment cases risk a defense argument that the named entity is not the operating employer of the relevant workforce. Verify which Amazon entity operates the specific fulfillment center at issue in your case before filing; Amazon.com Services LLC is the most commonly correct entity, but verify through the applicable Secretary of State’s database.

Why Professional Service Is Required for Amazon

Amazon’s entity complexity makes professional process service more consequential here than for virtually any other corporate defendant. A process server who delivers documents for “Amazon.com, Inc.” when the correct entity is “Amazon.com Services LLC” has not merely made a minor typographical error — they have delivered documents to a different legal entity. Amazon’s litigation team will move to quash service on that basis, and if the statute of limitations has run in the interim, the error may be irreparable. Our entity-identification review at intake catches this class of error before the server leaves the office.

Amazon’s registered agent is Corporation Service Company — not CT Corporation System. These are distinct organizations, and a server who appears at a CT Corp office with Amazon papers will be turned away. Our servers have established relationships with CSC offices in every major jurisdiction and are familiar with CSC’s intake protocols, documentation requirements, and processing timelines.

GPS-verified records are particularly important in Amazon litigation given the sophistication of Amazon’s outside counsel. Amazon retains national firms with dedicated process-service defense practice. A GPS-verified affidavit documenting the precise location, timestamp, and receiving party at the CSC office is materially more resistant to challenge than an unverified courier attestation. Our affidavits are formatted to the filing court’s requirements and delivered court-ready within 24 hours of service completion.

Our servers hold active DCWP process server licenses required for service within New York City’s five boroughs. Our network spans 120+ countries for Amazon’s international subsidiaries — Amazon Canada, Amazon EU S.à r.l. (Luxembourg), Amazon.com.au (Australia), and others — where Hague Convention or letters rogatory service is required for foreign proceedings.

Service Fees and Turnaround

All Amazon process service is priced at Tier 3 — our corporate complexity rate reflecting entity-identification review, CSC address verification, and GPS-documented delivery on every order.

Pricing covers one service attempt per entity. Multi-entity orders — for example, Amazon.com, Inc. and Amazon Logistics, Inc. in a DSP driver case — are priced per entity. Rush and same-day availability is subject to CSC office hours in the target state. Contact us to confirm turnaround before placing a time-sensitive order.

Frequently Asked Questions

“Amazon” is in my complaint caption — is that a problem?

Yes, it is a serious problem. “Amazon,” “Amazon.com,” and “Amazon Corporation” are brand names and informal references — none of them corresponds to a specific legal entity registered with any Secretary of State. A complaint captioned with any of these names as the defendant names nothing that can be served, nothing that can file an answer, and nothing that can be held to a judgment. Amazon’s outside counsel will identify this defect promptly and file a motion to dismiss for failure to name a proper defendant or for defective service. The correct defendant in most Amazon cases is Amazon.com, Inc. (for enterprise-wide and parent company matters), Amazon.com Services LLC (for marketplace and warehouse operations), Amazon Web Services, Inc. (for cloud disputes), Amazon Logistics, Inc. (for delivery cases), or another specific subsidiary. Your attorney should identify the correct entity before filing and caption the complaint accordingly.

Which entity do I sue for a defective product purchased through Amazon’s marketplace?

For marketplace product liability cases in California — and increasingly in other jurisdictions analyzing similar theories — the correct Amazon entity is Amazon.com Services LLC, following the California Court of Appeal’s August 2020 ruling in Bolger v. Amazon.com, LLC (53 Cal.App.5th 431). Bolger held that Amazon.com Services LLC is strictly liable as a seller in the distribution chain for defective products sold by third-party marketplace sellers. The product manufacturer is also a defendant and requires separate service. Note that if the item was sold directly by Amazon (not by a third-party seller), Amazon.com Sales, Inc. or Amazon.com Services LLC may be the correct direct seller entity. In jurisdictions that have not adopted Bolger-type marketplace seller liability, the analysis differs — the manufacturer may be the primary products liability defendant, with Amazon’s liability as marketplace platform being a more contested question. Consult your attorney to determine the correct entity and liability theory for your jurisdiction before filing.

My case involves an Amazon delivery driver — do I serve Amazon Logistics, Inc. or the DSP company?

Typically both, as separate defendants. Amazon Logistics, Inc. is the Amazon subsidiary that operates the Delivery Service Partner program and manages the last-mile delivery network. DSP companies are independently owned businesses that contract with Amazon Logistics to employ drivers and operate Amazon-branded vans. In personal injury and FLSA cases involving a DSP driver, the standard practice is to name and serve: (1) the DSP company, as the driver’s direct employer; and (2) Amazon Logistics, Inc., under general contractor or joint-employer theories. Amazon.com, Inc. may also be named as the ultimate enterprise defendant, though Amazon will typically defend that it is not the employer of DSP drivers and that Amazon Logistics operates the relevant program. Each entity requires independent service on its own registered agent through Corporation Service Company. Consult your attorney to confirm the appropriate parties based on the specific facts of the incident and the jurisdiction’s joint-employer or general contractor doctrine.

My dispute involves Amazon Web Services. Which entity do I serve and where?

For AWS disputes, the correct defendant is Amazon Web Services, Inc. — a Delaware corporation separate from Amazon.com, Inc. Service on Amazon.com, Inc. does not reach Amazon Web Services, Inc.’s legal team and will not satisfy service requirements for AWS matters. Equally important is the forum question: the AWS Customer Agreement designates Washington state law and grants exclusive jurisdiction to King County, Washington courts — or the Western District of Washington for federal matters. Commercial plaintiffs who file AWS disputes in other forums face a strong forum-selection-clause defense unless they can successfully challenge the clause’s validity or enforce an exception. Before filing an AWS claim, confirm with your attorney that you are naming Amazon Web Services, Inc. as the defendant, filing in the designated Washington forum, and serving through Corporation Service Company at the appropriate address. Service in Washington: CSC, 300 Deschutes Way SW, Suite 208, Tumwater, WA 98501.

My case involves a Whole Foods store. Is the defendant Amazon or Whole Foods?

For premises liability, slip-and-fall, employment, and consumer claims arising at a Whole Foods Market store location, the correct defendant is a Whole Foods entity — not Amazon.com, Inc. Whole Foods Market, Inc. is a Texas corporation headquartered in Austin, Texas, that was acquired by Amazon in August 2017 but retains its separate corporate identity. Naming Amazon.com, Inc. as the defendant in a Whole Foods store case is a common and avoidable error. Whole Foods Market Services, Inc. is a related entity providing HR and administrative services and may be the correct employer entity for employment claims. The correct Whole Foods operating entity for the specific store may vary by state. Consult your attorney and verify the applicable Whole Foods entity’s registration in the state where the store is located before filing. Registered agent for Whole Foods entities: Corporation Service Company at the applicable state address — verify with the Secretary of State before service.

What is Ring LLC, and when should I name it instead of Amazon.com, Inc.?

Ring LLC is an Amazon subsidiary — a Delaware limited liability company acquired in February 2018 — that manufactures and markets smart home security devices, including Ring video doorbells, security cameras, and alarm systems. Ring LLC is the correct defendant in product liability cases involving defective Ring hardware, cybersecurity vulnerabilities in Ring devices, and privacy class actions arising from Ring’s camera data practices. Cases involving Ring’s law enforcement data-sharing program — in which Ring allowed police departments access to doorbell camera footage — name Ring LLC. Amazon.com, Inc. may be named as the ultimate enterprise defendant in Ring class actions, but Ring LLC is the entity that designed, manufactured, and operates the Ring platform. The distinction matters for both service and for ensuring the liability exposure is correctly attributed to the entity that made the product decisions at issue. Ring LLC’s registered agent is Corporation Service Company. Its principal place of business is in Hawthorne, California.

Does Amazon’s HQ2 in Virginia affect where I serve Amazon?

HQ2 — Amazon’s second headquarters campus at 241 18th Street South, Arlington, Virginia 22202, opened in 2023 — does not change which legal entity is the correct defendant or where that entity’s registered agent is located. Amazon.com, Inc. remains a Delaware corporation with its principal office in Seattle, Washington; its registered agent in Virginia is Corporation Service Company, 100 Shockoe Slip FL2, Richmond VA 23219. HQ2 is operationally significant, not legally transformative. Where HQ2 does affect litigation strategy is in two specific contexts: first, employment disputes involving personnel who work at the Arlington campus may involve Virginia-based employment law claims (Virginia Human Rights Act, Virginia wage and hour statutes) that are filed in Virginia courts; second, AWS commercial matters for customers anchored in the Northern Virginia data center corridor may have Virginia connections that affect forum analysis even within the AWS Customer Agreement’s Washington forum designation. In both cases, the registered agent address for Virginia service is the Richmond CSC address above.

How long does Amazon have to respond after service?

Response deadlines depend on the forum. In federal court under FRCP Rule 12(a)(1)(A), Amazon has 21 days after service to file a responsive pleading — though in practice Amazon’s outside counsel almost always requests and receives a stipulated extension. In California state court, the standard response period is 30 days. In Washington state court under Washington CR 12(a)(2), the response deadline is 20 days for a defendant served within the state. In New York under CPLR § 320, Amazon has 20 days to appear when served through its registered agent. In New Jersey under N.J. Ct. R. 4:6-1(a), the response deadline is 35 days. These deadlines begin running from the date service is complete — not from the date proof of service is filed with the court. Amazon maintains national litigation management teams and responds to civil process on schedule in all jurisdictions. Do not assume that Amazon’s large size or litigation volume will produce delays in its response; the opposite is typically true, as Amazon’s outside firms are experienced, well-staffed, and closely track service dates.

Ready to Serve Amazon? Order Now

Undisputed Legal has served process on Amazon.com, Inc. and its subsidiaries — Amazon.com Services LLC, Amazon Web Services, Inc., Amazon Logistics, Inc., Ring LLC, and others — across jurisdictions nationwide. Our process begins with entity identification at intake, not after the server is dispatched. We catch entity mismatches, stale CSC addresses, and caption defects before they become motions to dismiss.

Our GPS-verified affidavits are court-ready within 24 hours of service completion and formatted to the specific requirements of the filing court. For high-stakes Amazon product liability, AWS commercial, antitrust, and employment matters — where Amazon’s outside counsel scrutinizes every procedural step — that documentation standard is not optional. A GPS-verified affidavit that survives a motion to quash does not need to be re-served.

Place your order through the widget below or call (800) 774-6922 to speak with our team directly. We confirm the correct Amazon entity, verify the current CSC address in your jurisdiction, and review applicable service rules before dispatch — so your service is right the first time.

WHAT OUR CLIENTS ARE SAYING

Ready to Serve Amazon? Order Now

Every day you wait is a day closer to a missed deadline. Statutes of limitations run. Discovery windows close. Amazon's legal team is already prepared — are you?

Order Service Online — Upload your documents and we begin immediately.
Call (800) 774-6922 — Speak with our team for rush or same-day service.
Email [email protected] — Send documents and we confirm within the hour.

Don't let improper service destroy your case against Amazon. Hire the professionals who do this every day.

Professional Credentials & Affiliations

Undisputed Legal Inc. maintains active membership and affiliations with the following professional organizations: National Association of Professional Process Servers (NAPPS), United States Process Servers Association (USPSA), National Association of Legal Support Professionals (NAOSP), Better Business Bureau (BBB) A+ Rating, New York State Unified Court System, DCWP Licensed Process Server (NYC), International Association of Professional Process Servers, National Notary Association, American Bar Association (ABA) - Allied Member, New York County Lawyers Association, Brooklyn Bar Association, Queens County Bar Association, Bronx County Bar Association, Staten Island Bar Association, Westchester County Bar Association, and Nassau County Bar Association.

Corporate Process Service Resources

Undisputed Legal is the authority in corporate process service. Explore our expertise:

• Complex Corporate Process Service — Advanced Legal Strategies
• How to Serve Business Entities — Corporate Process Service
• Corporate Process Service for Business Entities
• Registered Agents & Process Service — What Businesses Must Know
• Serving Legal Papers at CT Corporation — Step-by-Step Guide
• How to Serve Legal Papers at CT Corporation
• Understanding Registered Agents for Service of Process
• The Model Registered Agents Act and Service of Process
• National Conference of Commissioners on Uniform State Laws
• Corporate Process Service: Registered Agent Requirements
• Corporate Process Service: A Complete Guide
• Corporate Process Service Laws: Requirements & Compliance
• Complex Corporate Process Service Solutions
• Corporate Process Service: E-Service Requirements & Solutions
• Why Serve Legal Papers Through the New York Secretary of State
• How to Serve Legal Papers on the Delaware Secretary of State
• How to Serve Legal Papers on the New Jersey Secretary of State
• Process Service Rules & Laws: Serving Secretary of State
• New York State Process Server Regulations, Compliance & Liability

Get Directions to Our Manhattan Office