Layout FoundryDTF prices and material planners, home

For printers

Price feed and builder by website platform

To be verified, your website serves your feed file at /.well-known/layoutfoundry.json on its own address, or a DNS record on your domain names where the file is. Find out below whether your platform can serve the file.

Checked against each platform's own help pages on 26 Oct 2026.

What you need

  • A file at https://your-website/.well-known/layoutfoundry.json, on the same host as the website in your listing, with no redirect to another host. You can make the file on our price feed page.
  • Or, if your website can't serve the file, a TXT record on your own domain that names where you host it. Setting up the DNS record
  • For our builder on your own site, a page where you can paste two lines of HTML, one of them a script. The builder works only for verified printers. Turning on the builder

Being verified never changes the order of prices. Every list is sorted by the total price only.

Shopify shops can publish the feed from our Gang Sheets app instead. If your platform isn't listed here, the test is the same: open the file's address in a browser and check you see the file's text.

Platforms at a glance

A hand-built site

Can serve the feed file: Yes.

Your web server sends whatever is in its web root, so create a folder called .well-known there and put layoutfoundry.json inside it.

On GitHub Pages, Jekyll leaves out folders whose names start with a full stop. Add include: [".well-known"] to _config.yml, or add an empty file called .nojekyll to the site.

On Netlify, staff said in August 2024 that .well-known folders are now deployed. Some upload tools still leave out hidden folders, so open the address in a browser after each deploy.

Where the builder's two lines go

Paste the two lines into the HTML of the page where you want the builder, inside the body.

Sources

Shopware 6

Can serve the feed file: Yes, if you run your own server.

On your own server, the web root is the public folder. Put the file at public/.well-known/layoutfoundry.json.

Shopware's sample nginx settings refuse every address that starts with a full stop, including .well-known. If you use them, add a rule that allows /.well-known/ before that line. The sample Apache settings do not block it.

We found nothing in Shopware's documentation on adding files to a store on its cloud service, so we can't say whether a cloud store can be verified.

Where the builder's two lines go

The safest place is your theme: add the two lines to the page's Twig template.

A Shopping Experiences HTML element also works, but Shopware's HTML sanitizer, from version 6.5, can remove script tags. Shopware's documentation says to configure or turn off the sanitizer for HTML elements. On a self-hosted store that is shopware.html_sanitizer in config/packages; on the cloud service it can't be changed.

Sources

Gambio

Can serve the feed file: Yes, if you run your own server.

On your own server, create the .well-known folder in the shop's main folder by FTP or with the file manager in the Toolbox, and put the file inside it.

Gambio's manual says cloud shops have only limited FTP access. It doesn't say whether a .well-known folder can be added, so we can't say whether a Gambio Cloud shop can be verified.

Where the builder's two lines go

Add a page in the Content Manager and switch the editor to HTML before you paste the two lines. Open the page afterwards to check the lines are still there.

Sources

PrestaShop

Can serve the feed file: Yes.

PrestaShop runs on your own server. Put the file at .well-known/layoutfoundry.json in the shop's main folder.

PrestaShop's sample nginx settings block addresses that start with a full stop but leave .well-known open on purpose.

Where the builder's two lines go

A small module that prints the two lines on one page is the safest way, because the page editor cleans what you paste.

In a CMS page, the HTMLPurifier setting (Shop Parameters, General) removes script tags. Turning it off lets more through, for every editor in the shop, so only do it if you understand the risk. Open the page afterwards to check the lines are still there.

Sources

BigCommerce

Can serve the feed file: Yes.

You can't change the store's top folder, but BigCommerce lets you create a .well-known folder inside the content folder over WebDAV. A file at content/.well-known/layoutfoundry.json is served at /.well-known/layoutfoundry.json.

BigCommerce doesn't say which content type it sends for a JSON file. Open the address in a browser after uploading: you should see the file's text, not a store page.

Where the builder's two lines go

Use Page Builder's HTML widget on the page you want, or add the lines in Script Manager and choose the pages they load on.

Sources

Squarespace

Can serve the feed file: No.

Squarespace doesn't let you put a file at an address of your choice. URL mappings can't redirect file addresses, and a redirect to another host doesn't count as a feed.

So a Squarespace site can't serve the feed file itself. If your site uses your own domain, you can still be verified with a DNS record on that domain that names a feed file you host somewhere else. See the DNS record section on our price feed page.

Without a feed, your listing still shows your prices, checked against your price page each week.

Where the builder's two lines go

Once you're verified, a Code Block in HTML mode takes script tags. Squarespace runs JavaScript in Code Blocks only on its Core, Plus and Advanced plans.

Sources

Wix

Can serve the feed file: No.

A Wix site can't serve a file at /.well-known/. Asked about a file there, Wix staff said on its Velo forum that it can't be done with routers or HTTP functions, and later answers say the same.

So a Wix site can't serve the feed file itself. If your site uses your own domain, you can still be verified with a DNS record on that domain that names a feed file you host somewhere else. See the DNS record section on our price feed page.

Without a feed, your listing still shows your prices, checked against your price page each week.

Where the builder's two lines go

Wix's Embed code element runs code in a sandboxed frame, so the builder would not work there as it stands.

Sources