How it works
Most builds take two to three weeks once we have the information below and working Amrod API access.
The catalogue connection is tested first. There is little value designing the rest of the site before we know that your account is returning the correct products, prices and stock.
1. You send us the business information
We ask for:
| What we need | Why we need it |
|---|---|
| Logo | For the website branding and header |
| Company details | Registered name, registration number, VAT number if applicable, address, phone and email |
| Amrod account details | Username, password and customer code used for the catalogue connection |
| Starting markup | The default pricing rule used when the catalogue is first loaded |
| Trading terms | Lead times, delivery, payment and other terms that must appear on the site |
| Domain | The domain you want to use, or access to an existing domain |
Account credentials should be supplied securely and are used for the catalogue connection, not published on the website.
2. Amrod API access is confirmed
An Amrod reseller account and Amrod API access are not the same thing.
If API access has not been enabled on your account yet, we tell you what needs to be requested from Amrod. We can work on the website structure while that request is being handled, but the live catalogue cannot be tested until access works.
3. We test your catalogue connection
Before the main build, we confirm that the account returns:
- Products and variations
- Your account-specific prices
- Stock at variation level
- Categories and brands
- Product images and catalogue data
If the account or permission is wrong, this is where it is found.
4. The catalogue is imported
The site database is populated from your account and the sync schedules are configured.
Your starting markup is applied and checked against sample products before the catalogue is opened to customers.
5. The website is set up around the catalogue
We apply your logo, colours, company details, page content and trading terms.
The product pages, quantity grid, quote basket, customer accounts and forms are configured around the live catalogue rather than dummy products.
6. You review the private site
Before launch, you see the website on a private or staging address.
This is where we check:
- Selling prices
- Category structure
- Product display
- Stock presentation
- Quantity grid behaviour
- Quote requests
- Company details
- Website wording and policy information
Corrections are made before the domain is pointed at the site.
7. The site goes live
We connect the live domain, configure SSL and complete the launch checks.
Search engines are then allowed to crawl the public site and the sitemap is made available for indexing.
8. The scheduled updates start
After launch:
- A full catalogue refresh runs overnight
- Stock is refreshed during the day
- Changes are checked every fifteen minutes
- Your pricing rules continue to apply to new cost data
- Failed sync jobs are monitored on our hosted service
You can edit normal website and product content from the WooCommerce admin without rebuilding the integration.
What you still do after launch
The API is read-only. It does not place orders with Amrod.
Quote requests arrive with the product and variation information already organised, but your team still handles the final commercial work: branding, artwork, delivery, unusual lead times and placing the supplier order.
Ready to check your account?
If you already have an Amrod reseller account, contact us with your company name and current website situation. We can tell you what is needed before a build can start.