Your wholesale customers log in to your own site, see the collections you opened to them, and place their own orders. WebLink is the AIMS360 B2B portal.
WebLink is the AIMS360 B2B portal. Your retailers sign in, see the collections you opened to them, and place their own orders. It runs from inside the ERP, so the catalog, the prices and the customer list are the ones you already maintain.
A B2B wholesale ordering portal is a private website where the accounts you already sell to sign in and place their own orders. They browse your line, check what you have, key quantities across the size run, add a PO number and delivery dates, and submit. No phone call, no emailed spreadsheet, no order form typed up by somebody on your side afterwards.
It is not a shop. There are no public prices, no card checkout for strangers, and nobody can sign themselves up. You decide who gets a login and what each of them can see once they are in.
AIMS360 calls its version WebLink. Some of the documentation writes it Weblink. It is a browser based add-on to AIMS360, configured entirely from inside the ERP, and it shares its collections with RemoteLink, the rep facing iPad app.
Four moves, and one of them has an order of operations worth knowing.
The buyer signs in with an account number, a username and a password, all three sent by you. They land on whichever page you set for customer logins, usually Shop. From there they browse a collection or search a style, open the Stock link to check availability, key quantities across the sizes, then fill in the checkout header with their PO number, start and complete dates, and any notes they want on the confirmation. Place order sends a confirmation to them and to you.
Account number, username and password. The landing page is yours to set, and reps and customers can be sent to different ones.
Enter the Shop and browse the collections you opened to that account, or search a style number directly.
Open the Stock link first if you want the buyer to see calculated availability, then enter quantities next to each size. Add to Order with Quantities is faster but skips the availability view.
Customer PO number, start and complete dates, notes for the confirmation, then Place order. Addresses come from the customer record rather than being typed in.
| On the checkout screen | Detail |
|---|---|
| Three checkout views | Worksheet, style color, or style color size. AIMS360 recommends worksheet. Style color size hides any style with zero quantity, which confuses buyers at checkout. |
| Size grid entry | Quantities go in field by field against the size run, then save and close. |
| Cart edits | Add more items, or tag lines and remove the checked ones. |
| Customer PO number | Entered by the buyer. Reusing one they have already used triggers a warning at save. |
| Start and complete dates | Set per order by the buyer. |
| Notes | Free text the buyer wants printed on the order confirmation. |
| Addresses | Come from the AIMS360 customer record. A buyer who needs one corrected asks their rep, they cannot edit it themselves. |
| Confirmation | Emailed to the buyer and to you, normally inside a minute and up to five. |
Yes, and it is the strongest thing WebLink does. Mark a collection private and two extra tabs appear on it, one for salesreps and one for customers. Attach the accounts that should see it and nobody else does. An off price collection stays away from your full price accounts. A key account previews next season while everyone else sees current stock. A licensed range only reaches the territory allowed to buy it.
That sits on top of three other controls that apply to every collection: an Active switch, a start and end date, and separate checkboxes for whether the collection appears in WebLink, in RemoteLink, or in both.
| Make Collection Private | Turns on per collection. Adds a salesrep tab and a customer tab for attaching who may see it. |
| Who can see private collections | The admin login sees all of them. Everyone else needs a salesrep assigned to their AIMS360 login and needs to be attached to that collection. |
| Start and end date | A scheduled collection stays hidden before its start date, runs through the end date, and disappears the day after. |
| No Expiry | For anything that should stay up until you take it down. |
| Active | A quick on and off that does not require touching the dates. |
| Is for WebLink | Decides whether the collection appears on the buyer portal at all. |
| Is for RemoteLink | The same decision for the rep iPad app, set independently. |
Collections are built in AIMS360, not on the website. A collection has a parent and subcollections underneath it, and that is as deep as it goes: a subcollection cannot contain another subcollection. Parent names have to be unique, but subcollection names can repeat under different parents, so DRESSES can sit under SUMMER, SPRING and HOLIDAY at the same time.
Images are attached to the collection by browsing or by dragging onto the image grid. Where a style color image is missing you choose what the buyer sees instead: the default all color image for that style, or a no photo available placeholder.
The same catalog work feeds your line sheets, and the size and color structure behind it is covered on style, color and size.
Only if you decide they should. Showing availability to customers is off until you switch it on, and you can switch it on for reps and leave it off for buyers. A portal that shows no stock at all is a legitimate way to run this.
When it is on, know what the number means. The Stock figure defaults to the total available at the farthest date out, which is a forward projection including work in progress, not what is sitting in the warehouse this morning. A buyer who wants today types today's date and clicks Go, and on a lot of lines that figure comes back at zero. Neither number is wrong. They answer different questions, and it is worth telling your accounts which one they are looking at.
| Allow customers to see stock qty by delivery date | The switch that shows buyers availability. Off by default. |
| Allow sales rep to see stock qty by delivery date | The same switch for reps, set independently. |
| Default figure | Total quantity available to the farthest date out, based on what you include in the calculation. |
| What goes into it | You choose what the calculation includes, such as stock and work in progress. |
| Seeing today | The buyer enters a date and clicks Go. The calculation ignores order completion dates beyond the date selected. |
| Multi warehouse | You choose which warehouses feed the figure the portal shows. |
| Pending web orders | Orders placed on the portal but not yet imported are left out of the calculation unless you turn that option on. |
Prices come from your Classic price sheets, which carry tiered pricing, price by size and customer level pricing. A discount set on a customer's record follows that account onto every order without anyone applying it. With a net discount the buyer only ever sees the net price, with no discount detail shown at all.
Three discount types can be enabled on the portal, separately for reps and for customers: line item, net and discretionary. Every discount taken requires a reason code, which carries through to the order and prints on the confirmation. AIMS360 documentation is blunt about customer side discounting, and so are we: think carefully before letting buyers set their own.
| Discount type | How it behaves |
|---|---|
| Line item | Applied to tagged styles at a selected code and rate. The line shows original price, discount and new price. |
| Net | An order level discount. Cannot be combined with a line item discount on the same order. |
| Discretionary | Can be used in addition to a line item discount. |
| Reason codes | Required on every discount, set up once in AIMS360 and reportable afterwards. |
| Customer level | Set on the customer record and enforced on every order that account places. |
Yes. Reps get their own login, their own landing page and their own view. A rep selects the customer before starting an order, and the addresses come from that customer record, so an order written by a rep and an order placed by the buyer arrive the same shape.
Access is deliberately tight by default. A rep reaches the customers where they are the primary rep, and nothing else. A second rep on an account needs a system setting switched on. A rep who needs everything can be given access to all customers on their own WebLink login tab.
| Rep landing page | Set separately from the customer landing page. |
| Ordering on behalf | The rep picks the customer first, then orders as that account. |
| Customer visibility | Primary rep by default. Second rep and all customer access are both switchable. |
| Customer master access | A switch for whether reps can reach customer records from the portal. |
| Stock scope for reps | Reps can be limited to portal styles, or allowed to run availability across all styles. |
| Rep reporting | Sales activity and order or invoice statistics can be turned on for reps. |
| Rep mapping | Customer map and distance map for planning a road trip, using a Google Maps key. |
If your reps write orders in person rather than at a desk, that is RemoteLink, which runs on an iPad and keeps working with no signal. Rep earnings are covered on sales rep commissions.
Into the Web Orders module in AIMS360, as a complete order. The line detail, the size breakdown, the customer PO, the dates, the notes and any discounts are all on it. Somebody on your side then imports it, which is the point it picks up an AIMS360 order number and joins your order book.
That import step is real and we would rather you hear it from us. On a buyer facing channel it earns its place: it is where a credit problem gets caught, where a duplicate PO gets compared against the original before anything is committed, and where an order placed by an account you have just put on hold does not quietly become a shipment. What nobody does at any point is re-key a line.
Everything else about being part of the ERP still holds. There is no middleware between WebLink and AIMS360, no connector to buy, no second vendor to call. Orders land on the same master stock record as your EDI, DTC and rep written business.
| The assumption | What is the case |
|---|---|
| A B2B portal is a separate product you integrate | WebLink is an AIMS360 module, from the same company, on one contract with one support team. There is no connector. |
| Orders appear in the ERP on their own | They arrive complete in the Web Orders module and are imported from there. That review step is by design on a buyer facing channel. |
| Somebody re-keys the order | No. The order arrives with its full line detail, dates, PO and discounts already on it. |
| Terms and ship via have to be set on the portal | From version 25.04.23 standard fields like terms and ship via are taken from the customer record at import if they were not set on the portal. |
| A buyer can change an order after placing it | Only if you allow edit and void, and only before import. Once imported, those controls disappear. |
| It behaves like the rep app | It does not. RemoteLink orders import straight into Customer Orders. WebLink orders go through the Web Orders queue. |
These get discussed as if they were the same decision. They are not.
A marketplace puts your line in front of buyers who have never heard of you, alongside everyone else's. That is worth paying for when you are opening new accounts. The trade is that the marketplace holds the relationship and takes a share of what sells.
Your own portal does the opposite job. Only your line is on it, only the accounts you gave logins to can reach it, nobody takes a cut, and the buyer is dealing with you. That fits the accounts you already have and want to keep serving efficiently.
Most brands past their first few seasons end up doing both: a marketplace for discovery, their own portal for the book of business that already exists. AIMS360 connects to the major B2B platforms as well, and the rep facing side is covered separately.
Catalog first, access second, then the logins. Budget time for the mail server step, because nothing sends until it is done.
In the Collections module create a parent collection and its subcollections. Nesting goes two levels, so a subcollection cannot hold another subcollection. Tick Is for WebLink on anything the portal should show.
Mark the collections that are not for everyone as private, then attach the specific salesreps and customers who should see them. Set a start and end date, or no expiry, on anything seasonal.
On the WebLink Settings Stock tab, decide whether customers see availability at all, and which warehouses feed the figure. This is off by default, so a portal with no stock shown is a valid choice.
Confirm your Classic price sheets are set so wholesale prices show automatically, then use the Discount tab to decide which discount types reps and customers may apply. Reason codes are required on every discount.
Enter your SMTP host, username, password, from address and port in general settings, and set the internal notification address in AIMS360 company settings. Nothing sends until this is done.
Add a login on each customer's WebLink Logon tab, or run Auto Create Customer Logins to tag many customers and send their credentials in one action. Buyers sign in with an account number, username and password.
Better to know these while you are scoping than after you have told your accounts.
Buyers cannot sign themselves up. Every login is created by you, one at a time or in bulk. There is a separate prospects feature for capturing someone who is not a customer yet, but the ordinary path is that you issue access.
There is no oversell block. Nothing stops two accounts being shown and sold the same units while orders sit in the queue unimported. Plan your availability settings around that.
Orders do not import themselves. They arrive complete in the Web Orders module and someone imports them. The rep app works differently, and that difference is deliberate.
The newer pricing engine is not available here. Price Categories and Price Tiers do not currently work with WebLink. Portal pricing runs on Classic price sheets.
Mobile is not documented. The documentation does not cover phone or tablet use, so we do not claim it. Tablet order writing is RemoteLink.
It sends through your mail server, not ours. You supply SMTP host, username, password, from address and port. That means confirmations come from your domain, and it also means deliverability is yours to get right.
Branding is a logo and custom pages. You can replace the default logo, set its alignment and add custom pages. Treat anything deeper as an implementation conversation rather than a self service setting.
Catalog nesting stops at two levels. Parent collection and subcollection. A subcollection cannot contain another subcollection.
Sessions end after an hour. There is a configurable timeout, but AIMS360 disconnects any idle session after an hour across AIMS360, WebLink and RemoteLink to stay inside PCI and similar compliance rules.
It is an add-on module. WebLink is not part of the base system. Ask your AIMS360 contact what it looks like for your account.
What brands ask before opening a portal to their accounts.
You create it. There is no public sign-up. Open the customer in AIMS360, go to the WebLink Logon tab, add a user ID, password and email address, and tick Email Logon and Password to User.
For a whole customer base at once, use Auto Create Customer Logins in the WebLink module: tag the customers, apply settings, and send the logons in one action. Every customer needs a valid email on their record first.
Yes, and this is the part most brands come for. Mark a collection as private and two extra tabs appear where you attach specific salesreps and specific customers. Only those accounts see it when they log in.
On top of that, every collection has an Active switch, a start and end date, and separate checkboxes for whether it appears in WebLink and RemoteLink. A key account can see next season while everyone else sees current stock.
Only if you switch it on. Allow customers to see stock qty by delivery date is off by default, so you can run the portal with no availability shown at all.
When it is on, be aware of what the number means. The Stock figure defaults to the total available at the farthest date out, not what is in the warehouse today. To see today, the buyer types today's date and clicks Go.
Nothing blocks the second one. WebLink has no documented oversell prevention, and orders that have been placed but not yet imported are left out of open to sell calculations unless you turn on the pending web orders option.
This is worth designing around. Brands running tight inventory usually show availability against a forward delivery date rather than today's on hand, and import the queue often.
Into the Web Orders module in AIMS360 as a complete order, with the line detail, the customer PO, the dates and any discounts already on it. Somebody then imports it, which is when it gets an AIMS360 order number.
That review step is deliberate on a buyer facing channel: it is where you catch a credit problem or a duplicate PO before the order reaches your order book. Nobody re-keys a line either way.
Different person, different moment. WebLink is buyer facing, for the account that reorders on its own at 11pm. RemoteLink is rep facing, for the order your rep writes in person in a showroom or a booth.
Most brands with an active wholesale business run both, and they share the same collections: one checkbox decides whether a collection appears in WebLink, RemoteLink or both.
No, and that is the point. A marketplace hosts your line alongside everyone else's, owns the buyer relationship and takes a cut of the order. WebLink is your own portal, reached by a private link, with only your line on it and only the customers you gave logins to.
The two are not exclusive. Plenty of brands use a marketplace to find new accounts and their own portal to service the accounts they already have.
Yes. Reps get their own login and their own landing page, and a rep picks the customer before starting an order, with addresses pulled from that customer record.
By default a rep only reaches customers where they are the primary rep. A second rep needs a system setting switched on, or you can give a specific rep access to all customers on their WebLink login tab.
Yes, if you allow it. Tick Allow User To Create Orders for Any Store Location on that login and a store dropdown appears at order time. Leave it off and the buyer is limited to the one store their login is tied to.
Prices come from your Classic price sheets, which handle tiered pricing, price by size and customer level discounts. A discount set on the customer master carries onto every order automatically.
You can also enable line item, net and discretionary discounts, separately for reps and for customers, and every discount taken requires a reason code. One caveat worth knowing before you plan a rollout: the newer Price Categories and Price Tiers engine does not currently work with WebLink, so pricing here runs on Classic price sheets.
Yes. WebLink has an invoice view scoped to the logged in customer, so an account can check what they have been billed without emailing your AR desk.
The portal warns them at save. They can cancel and change it, or proceed anyway. If they proceed, you get a Compare screen at import that puts the new order and the existing one side by side so you can decide what happens before anything lands in AIMS360.
You can replace the default logo with your own, set how it aligns, and add custom pages. Treat deeper theming as a conversation with your implementation specialist rather than something documented as self service.
The documentation does not cover phone or tablet use, so we do not claim it. If your reps need to write orders on a tablet, that is what RemoteLink is for, and it works offline.
It sends through your mail server, not ours. You supply the SMTP host, username, password, from address and port in WebLink general settings, so order confirmations arrive from your domain.
Confirmations normally land inside a minute and can take up to five. One internal copy goes to the address in your AIMS360 company email settings.
It is an add-on module rather than part of the base system. Your AIMS360 contact can confirm what it looks like for your account.
Last reviewed 17 August 2026 by the AIMS360 product team.
Reviewed against the current AIMS360 WebLink documentation, covering collections and private collections, the stock and open to sell settings, Classic price sheet pricing and the three discount types, salesrep access rules, customer login creation, the checkout display options, and how orders reach the Web Orders module for import.
See WebLink running against your own collections, your own price sheets and your own customer list, in a demo built around how your brand sells wholesale.
