Digital line sheets as collections: merchandised groups of styles with images, colors, sizes and prices, built once from the style master and sold from on the rep iPad app, the B2B buyer portal and JOOR.
In AIMS360 a line sheet is a collection: a merchandised group of styles with the images, colors, sizes and prices already on them, built from the style master inside the ERP. Reps browse it on the iPad app, buyers order from it on your B2B portal, and it can feed a marketplace line sheet. One catalog, three places to sell, nothing re-keyed.
A line sheet is the wholesale catalog a brand shows retail buyers: each style with its number, name, image, colors, sizes, wholesale price and delivery window, arranged so a buyer can pick and write an order. It used to be a printed book or a PDF sent before market. Now it is mostly digital, and the buyer or the rep orders straight from it.
In AIMS360 the line sheet is a collection. You group styles from the style master into a named collection, give it dates, decide who can see it and where, and the images, colors, sizes and prices come with the styles. That collection is what the rep app browses, what the buyer portal shows, and what a JOOR line sheet is built from.
| Element | Where it comes from |
|---|---|
| Style number and name | The key the buyer writes on the PO and the warehouse picks against. In AIMS360 it is the style master, so the line sheet cannot drift from what you can actually ship. |
| Images | A default image for the style, plus an image per color, and the option to use a different image for the buyer portal than for your own online store. |
| Colors and sizes | The color list and the size scale the buyer orders across. They come from the style, so the grid the buyer sees is the grid the order lands on. |
| Wholesale price | From the price lists you already maintain, including customer specific pricing on the portal, so the buyer sees their price rather than a generic one. |
| Delivery window | A start and end date on the collection, and delivery dates on a line sheet that goes to a marketplace. Buyers order into the window, not around it. |
| Season and division | The collection can represent a season, a division, a delivery or any grouping that makes the line easier to sell, two levels deep. |
| Availability | Optional. Open to sell by date can be shown to reps, to buyers, to both or to neither, and you choose what the number includes. |
Every one of those lives on the style or the collection, which is the point. The size and color structure underneath is covered on styles and colors; selling by ratio rather than by size is on prepacks and case packs.
Reps browse collections with style and color images, search a style number or scan a barcode, check open to sell by date, key quantities on the size grid and write the order in the appointment. Works offline and uploads when it reconnects.
Your accounts sign in to your own site, see the collections you opened to them, and place their own orders against your live catalog. Private collections decide which accounts see which line.
Create a line sheet in AIMS360 with delivery dates and a season, attach it to the styles you export, and it is created and activated in JOOR with those styles on it. Orders come back with the season matched.
Customer service builds orders from the same styles in the ERP, and the reports that carry image options show the line with pictures for an internal review or a buyer who wants paper.
| Control | What it does |
|---|---|
| Parent and subcollection | Two levels, no deeper. A parent holds no styles of its own and exists to group subcollections. Parent names must be unique; subcollection names can repeat under different parents, so Dresses can sit under Summer, Spring and Holiday at once. |
| Start and end date | A scheduled collection stays hidden before its start date, runs through the end date, and disappears the day after. Set no expiry for a core line that stays up until you take it down. |
| Active | An on and off switch that pulls a collection immediately without touching the dates. New collections are active by default. |
| Rep app and buyer portalPer channel | Separate checkboxes for whether the collection appears on the rep iPad app, on the buyer portal, or both. The rep app box has to be ticked for reps to see it at all. |
| Private collection | On the buyer portal, mark a collection private and two tabs appear, one for sales reps and one for customers. Attach who may see it and nobody else does. The admin login sees everything. |
| Orders on out of stock items | A per collection setting that allows orders on styles with no stock, which is how a future delivery gets sold before it lands. If a style also sits in another collection, that collection's setting can override this one. |
| Add new styles automatically | An option that drops every new active style into a chosen collection as it is created, finished or not. No filters, so it is for making sure reps can always find a new style, not for routing by division. |
Styles are added to a collection through the same sort, filter and tag selection you use everywhere else in AIMS360, so a season, a division, a fabric group or a tagged list becomes a collection in a couple of clicks.
One image that represents the style in every color. It is what a buyer sees before choosing a color, and what the catalog falls back to when a color has no image of its own.
Each color of a style carries its own images, added on that color, so the buyer looking at Ivory sees Ivory. A missing color image shows the default or a no photo placeholder, your choice.
Each image is ticked for the channels it belongs to, so the buyer portal can show a flat lay while your online store shows an on model shot. A sequence number sets the primary image; sequence one is the default.
Keep files under about 4 MB. AIMS360 does not resize images, and oversized files slow the style master and every report with an image option. Name files with letters, numbers, hyphens and underscores only. Anything else can fail to upload. Give the primary image a sequence of one. An image with a sequence of zero is not sent to the portal or the rep app, so a style that seems to have lost its photo usually has a sequence problem, not a missing file.
Images can be added one at a time on the style, in bulk through the multi image import, or through the API, which also returns image URLs for anything you build on top.
AIMS360 has a JOOR line sheet module, so a line sheet can be created here and activated there without building it twice. It is worth knowing the four rules that come from how JOOR works, because they shape how you set the line sheet up.
Name, delivery dates, season and year, and whether it is visible to all by default. Delivery dates are required because JOOR needs them; if you remove them on the JOOR side, the next export puts them back.
A line sheet only reaches JOOR when it is associated with styles being exported or updated. Export by style and every color of that style goes onto the line sheet together.
On JOOR one order ties to one line sheet, and a line sheet carries one season. Keep each line sheet to styles from a single AIMS360 season and imported orders come back with the right season on them.
Single colors of a style cannot be split across line sheets from AIMS360; add or remove them on the line sheet in JOOR. Core styles that stay up for a long time are easier managed there too. A line sheet name locks once it has been exported.
Line sheets created on the JOOR site itself are not visible from AIMS360, so create them here if you want to manage them here. Full detail on the connection, including how orders and inventory move, is on the JOOR integration page. Brands on other platforms see NuORDER and Brandboom.
A default image per style and images per color, primary image at sequence one, ticked for the channels that should show them. Do this first; a collection without images is a price list.
Name it, give it a start date and an end date or no expiry, and tick the rep app, the buyer portal, or both. If it is a parent, leave it empty and add subcollections under it.
Use the style selection prompt with sort, filter and tags to pull in the season, the division or the tagged list, and the styles appear on the collection styles tab.
On the portal, make it private and attach the accounts and reps if it is not for everyone. Decide whether out of stock styles can be ordered from it.
Reps download the data to the iPad, buyers see it at sign in, JOOR gets it on the next export. When the season is done, let the end date close it or flip active off.
AIMS360 does not include a page layout tool for a designed PDF catalog. It holds the data and the images, reports with image options print the line, style data exports to Excel, and images come through the API. Brands that still send a designed PDF build it in their design tool from that export, and use the collection for actual ordering.
Parent and subcollection. If your merchandising needs a third level, use naming or tags inside the subcollection rather than expecting a deeper tree.
The option that adds new styles to a collection automatically adds every new active style. It is not a rule engine, and it will put unfinished styles in front of reps if that is what you create.
Open to sell is off for buyers until you turn it on, and the default figure is total available at the farthest date out, not what is in the warehouse this morning. Tell your accounts which one they are looking at.
A line sheet is the wholesale catalog a brand shows to retail buyers: each style with its number, name, image, colors, sizes, wholesale price and delivery window, laid out so a buyer can pick and write an order. Traditionally it was a printed or PDF document sent before market. Today it is usually digital, so the buyer or rep orders straight from it.
As collections. A collection is a merchandised group of styles built inside AIMS360 from the style master, with images, colors, sizes and prices already attached. The same collection is what your reps browse on the iPad app, what your buyers see on the B2B portal, and what feeds a line sheet on a marketplace like JOOR. You build the line once, in the ERP, and every channel sells from it.
The useful test is whether the line sheet and the order share one product record. In AIMS360 the collection is built from the style master, the rep app and the buyer portal order from that collection, and the order lands on the same customer record that holds terms, pricing and history. There is no export to a separate catalog tool and no re-keying of orders back in. Brands that also sell on a marketplace connect it, so those orders arrive the same way.
Yes, on the B2B portal. Mark a collection private and attach the customers and sales reps allowed to see it. An off price collection stays away from full price accounts, a key account previews next season while everyone else sees current stock, and a licensed range only reaches the territory allowed to buy it.
Yes. Collections go two levels deep: a parent, which holds no styles itself, and subcollections under it. Parent names have to be unique; subcollection names can repeat under different parents, so Dresses can sit under Summer, Spring and Holiday at the same time. A subcollection cannot contain another subcollection.
Three ways, and they stack. Give the collection a start date and an end date, or set no expiry so it stays up until you take it down. Flip the active switch to pull it immediately without touching the dates. And tick, separately, whether it appears on the rep app, the buyer portal, or both.
They can, and they do not have to. Every collection has a separate checkbox for the rep app and the buyer portal, so a collection can be rep only, buyer only, or both. On the portal, private collections narrow it further to named accounts and reps.
That is a per collection setting. You can allow orders on items that are out of stock at the collection level, which is how brands sell a delivery that has not landed yet. One caution: if a style also sits in another collection, that collection's setting can override this one, so keep pre-order styles in their own collection.
From the style record. Each style has a default image that represents the style in every color, and each color can carry its own images. You choose which channels each image is used for, so the buyer portal can show a flat lay while your online store shows an on model shot, and a sequence number sets which image is primary. Keep files under about 4 MB, because AIMS360 does not resize them and large files slow the catalog down.
You decide what the buyer sees instead: the style's default image, or a no photo available placeholder. Either way the style still appears and can still be ordered. An image with no sequence number, or a sequence of zero, is not sent to the portal or the rep app at all, so a style that seems to be missing its photo usually has a sequence problem rather than a missing file.
Yes, as an option on the collection. When it is on, every new active style created in AIMS360 is added to that collection, whether or not its images and details are finished. There are no filters on it, so it is not a way to route styles by division; it is a way to make sure reps can always find and add a brand new style to an order.
Only if you turn it on, and separately for reps and for buyers. When it is on, the figure is open to sell by delivery date, and you choose what goes into it, including work in progress and which warehouses count. The default figure is the total available at the farthest date out, which is a forward view; a buyer who wants today enters today's date.
Yes. AIMS360 has a JOOR line sheet module: name the line sheet, give it delivery dates, a season and a year, then attach it to the styles you export and it is created and activated in JOOR with those styles on it. Delivery dates are required because JOOR needs them. Line sheets created on the JOOR site itself are not visible from AIMS360, so create them here if you want to manage them here.
Because on JOOR one order is tied to one line sheet and a line sheet carries one season. If each JOOR line sheet holds styles from a single AIMS360 season, orders imported from JOOR come back with the matching season on them. Styles set to year round come back as any season.
Not from AIMS360 when you export by style, because all colors of the style go with it. Export the style, then add or remove individual colors on the line sheet inside JOOR. The line sheet name also locks once it has been exported, so name it carefully the first time.
AIMS360 does not include a page layout tool for designed PDF line sheets, and we would rather say so than imply one. What it does give you is the data and the images in one place: several reports have image options, style data exports to Excel, and images are reachable through the API. Brands that still send a designed PDF build it in their design tool from that export, and use the collection for actual ordering.
The rep app runs on iPad and keeps working without a connection for browsing collections, style images and writing orders, then uploads when it reconnects. The buyer portal runs in a browser and needs a connection. Neither is a phone app.
Images on the styles, with a sequence number of one on the primary image. A collection with a name, a start date or no expiry, and the rep app or portal box ticked. Styles added to it through the usual sort, filter and tag selection. And, on the portal, the customers attached if it is private. Most brands have a season's line sheet live in an afternoon once the images exist.
Show us the styles, the images and how you want buyers and reps to see them. We will build the collection in front of you and show you the same line on the iPad, on the portal and on the marketplace, without anyone typing it twice.
