Skip to main content

Spanx Collects Traceability Documentation From 90+ Suppliers on Files.com With Zero External Accounts

Supplier-specific upload pages capture style numbers with each file, then move every submission into SharePoint and delete it from the external site within five minutes.
SPANXFiles.com

Spanx invented modern shapewear. Founded in Atlanta in 2000 around a patented footless pantyhose, the company created the category it still leads, and it has since grown into a lifestyle brand selling shapewear, intimates, denim, activewear, and swim through wholesale and direct-to-consumer channels in more than 50 countries. Its products carry an unusual amount of engineering for apparel: patented constructions, bonded fabrics, and fiber technology developed with partners like The Lycra Company.

All of that is made through a supply chain of more than 90 external supplier and vendor companies. And every garment those companies produce for Spanx comes with a paper trail: traceability records, certifications, and ethical-sourcing affidavits that Spanx's Production team has to collect from companies it does not control.

Collecting From 90 Companies Meant Administering 90 Companies

Collection was manual and ad hoc. Every conventional way to systematize it started with the same tax: create and administer login credentials for every one of those 90-plus companies. Standing up and supporting accounts at that scale was itself the constraint on collecting the documentation at all, and the cost grew with every supplier Spanx added.

The documents that did come in could not reliably be tied to the thing they described. What Production needed was the style number, or set of style numbers, each document covered. The sender was the wrong key for that. Several people at one supplier might submit on their company's behalf, so the person changes while the company and the style must not. And when identification depended on what a submitter typed, the filing split: "XYZ Textiles, Inc" and "XYZ Textiles" land as two different vendors, and someone reconciles them by hand.

There was a third cost. These are compliance records, and a collection system that left them sitting on an internet-facing platform was exposure Spanx did not want to carry.

One Inbox Per Company, and a Form Field Instead of an Account

The fix had to be a standing intake point for each supplier company that anyone at that company could use without a credential. It had to capture identity as data traveling with the file, the style numbers and one canonical vendor name, rather than as a login. And it had to deliver every document into SharePoint, the system of record for vendor compliance documentation, without leaving a copy on the internet-facing system.

Spanx selected Files.com to be that collection layer, and built roughly 90 Files.com Inboxes, one for each supplier company. An Inbox is a permanent upload page. A supplier follows the link, fills in a short form, and submits, with no account behind any of it.

The design does three jobs at once. It makes the company, not the person, the unit of identity: whoever at a supplier submits this season, the file lands in that company's one inbox, so there is no free-text company field for two spellings to diverge in. It puts the style number on every file: custom form fields ask the submitter which style numbers a document covers, so the detail Production files by arrives attached to the upload instead of being reconstructed afterward. And it keeps the archive off the internet-facing system: Files.com Automations move every submission into SharePoint, mounted directly as a remote server, and delete the file from the Files.com site within five minutes of the transfer.

The whole external surface runs under Spanx branding, so a supplier sees a Spanx page rather than a third-party tool. And through all of it, Spanx created no external accounts. None of the 90-plus companies has a credential to issue, reset, or revoke.

In SharePoint Within Five Minutes, and Nowhere Else

With the inboxes in production, Spanx replaced ad hoc, hand-administered collection with a standing intake surface for its entire supplier base.

  • Documentation flows in from more than 90 external companies with zero external account administration. The overhead that had been the constraint on collecting at all no longer exists.
  • Every document arrives keyed to the style numbers it describes and files under a single canonical vendor, so Production can pull what is on record for a style without reconciling variant company names first.
  • Ethical-sourcing and certification records live only in SharePoint. The internet-facing system holds a document for no more than five minutes, by design.
  • Onboarding the next supplier means creating another inbox, not provisioning and supporting another company's users. The intake surface grows with the supply chain without growing the administration behind it.

Identity Moved From the Login to the File

Supplier documentation looked like an account-administration problem, and at 90-plus companies it was one that scaled with the business. Files.com let Spanx move identity off the login and onto the file itself: a form field now carries what a credential would have, and the credential never has to exist.