Prepare product identities, technical data and files before building a manufacturer BIM catalogue. Then use the BIMNESNE company panel to create drafts. This guide helps manufacturers move from a small pilot group to a larger catalogue and understand how company approval affects the subscription start date.
Start with a small product group
Choose five or ten related products as a pilot. Once their codes, dimensions and documents are consistent, extend that structure to the larger catalogue. Consider how a designer will find the product and change its types rather than combining the entire range into one large model. Decide which variations belong to types and which deserve separate product records before publication starts.
| Preparation | Deliverable | Internal owner |
|---|---|---|
| Identity | Reference code, TR/EN names, series | Product manager |
| Technical data | Dimensions, units, materials, document revision | Technical team |
| Model | Target application and test record | BIM content team |
| Publication | Image, description, files and final review | Company official |
Maintain one product reference
If a window is A-014 in the website catalogue, A14 in its file and carries an old name in a document, users have to resolve the discrepancy themselves. Maintain one reference list. Give dimensions as values with units and support performance claims with an identifiable document. A clear product title is more useful than a string of search keywords.
Turkish and English descriptions must represent the same product. Do not change units, model codes or technical values during translation. Use the product data checklist to assign ownership of missing information.
Create BIMNESNE drafts in bulk
Download the CSV template from Products > Bulk Product Import in the company panel. It contains four fields: reference_code, product_name_tr, product_name_en and category_id. You can edit it in Excel, then save as UTF-8 CSV. This import does not accept XLSX workbooks or media URLs.
- Format reference codes as text so leading zeros remain intact.
- Provide a product name in at least one language and a valid existing subcategory ID. Download the ID list from the import screen.
- Resolve validation errors in the preview. Previewing does not create products.
- Confirm the rows to create drafts, then complete images, files and other information in the product editor.
The limits are 5 MB and 5,000 rows per file. The browser processes small batches; keep the window open until it finishes. Drafts count towards the plan quota. Reference codes already used by the company, including deleted products, are skipped rather than imported again. Importing does not update existing products. Publication still follows the normal company and product approval process.
Review the pilot before scaling
Match the pilot product's description, cover and download to the same reference. Run the placement checks and assign a person to maintain revisions. A useful final review has a recorded decision: ready, needs a technical answer or needs a file correction. That lets the next editor continue without repeating the investigation. Begin the publishing process on the company registration page.
Company approval and your plan start date
When creating a company, you can select the free trial or an available paid plan. The 14-day free trial begins when the company is approved. A paid period begins after payment is verified and the company is approved. Unused trial entitlement is added to the first paid period; if the trial has not started, that entitlement is 14 days. Selecting a plan does not verify payment.
Time does not run while company approval is pending. Account email verification is a separate process. If a period expires without payment, products are hidden from the public catalogue while content and editor records are retained. Check Plan/Billing for currently available payment options.
Sources and editorial note
See Autodesk's family guide for model concepts and the buildingSMART IDS overview for information requirements. The import steps describe BIMNESNE's current CSV workflow; they do not promise automatic model or IDS validation. The cover is a conceptual illustration.