Connections

What we would read: Your quotes, your customers, your items, and the status of each quote.

What we would write: Nothing, to begin with. Later, one thing only — a draft quote created from an AGi32 schedule, which a person previews and approves before it exists in NetSuite.

Why this one is straightforward: NetSuite has a properly documented way in, and an AI connector included in your subscription at no extra cost. Most systems we meet have no way in at all, so this is unusually good ground.

To go live: An administrator creates a read-only integration record and access token. About an hour of someone's time.

What we would read: The quotes that go out, and the replies that come back on the same thread. Nothing else — not internal mail, not unrelated conversations.

What we would write: One thing. A follow-up that a person has read and clicked send on, from that person's own address.

Why it matters: This is the connection that makes the difference. NetSuite knows a quote was sent. Only Gmail knows whether anyone replied.

To go live: Each quoter connects their own mailbox once.

The honest position first: AGi32 is desktop software with no API, and Lighting Analysts do not publish one. Nothing can talk to it directly. Any supplier who tells you otherwise is guessing.

But there is a way through, and it does not need the vendor's help.

Every fitting you define in AGi32 carries fields that are yours to fill in — Label, Description, Tag, and custom attributes. Put your NetSuite item code in the Tag field.

AGi32 already ships a schedule type called Luminaire Tag Summary, and its output is two columns: Tag and Quantity. With your item code in the Tag, that schedule becomes a list of NetSuite codes and how many of each — rolled up across every arrangement on the job, generated by AGi32 itself, and updated automatically as the design changes.

Export that, and it becomes a draft quote.

What it changes: The design still takes as long as it takes. The hour afterwards, rebuilding the fitting list into a quote by hand, mostly disappears.

What it needs: One master library. A single AGi32 job file holding every product with the right photometric file and the right code, that designers import from rather than building their own. That is the piece worth doing first, and it is a project rather than a switch.

What it could do: Post a collision into your New project check-in channel the moment one is found, so the question gets answered before anyone has to ask it.

Fixture names typed onto plans are downstream of the product library above. Fix the library and this looks after itself.

Worth noting because it is the pattern. An order arrives, a customer record and a sales order appear in NetSuite, the store fulfils it. Everything on this page is that same idea applied to quotes instead of orders.