Changelog

2026-11-02

• Revision requests: a change that names a line by its tag or line number now lands on that line, so an accepted quantity, removal or line discount is written to it, and a line discount no longer becomes a discount on the whole quotation. One tag of a line holding several, or a tag on two lines, reads Edit by hand. A plain value followed by a full stop, such as “45 days.”, reads the same as one without, and a correction such as “8 Nos, not 6” reads as 8. A comment typed on a PDF that the reader left out, and a line pointing only at a call or at an attachment the email does not carry, are now listed for a person, and an email whose file speaks of marks that could not be read says so. See Revision requests.
• Inbox: a client’s email typed Other and linked to an enquiry is now read for what it asks to change, so a moved bid date or a regret is listed. An email FlowOS is unsure of that answers a quotation made outside FlowOS, such as a returned quote with a thin cover note, is now linked and read instead of waiting in Needs Review (R7).
• PO check: a wrong order code on a product whose code ends in an accessory now names the option that differs, and a code that is not ours, such as another maker’s, is an Open row where it used to read Matched. The taxable total may carry the charges the PO states or the quotation bills, so a clean PO with packing no longer opens PO arithmetic. A line’s amount the reading left out is taken from its row, a printed order discount the totals bear out is kept, a packing row is no longer read as a discount, packing or freight counts as included only when the PO says so, a delivery that “will be advised” is open, and an email with several POs no longer loses one when the reading miscopies a file’s reference. See Checking a purchase order.
• Inbox: an open conversation now fits a laptop screen. On a window under 1800 pixels wide the email list opens folded to its strip until you choose otherwise, the email is drawn at 90% of its sender’s size, its header keeps each field to one line, with the full text on hover, and the enquiry reading takes less height. In the lines pane each line keeps its product on one row, with its facts, then smaller Suggested and review state chips, on the next, in slightly smaller type, and the category shows only on an excluded line, since the product names it on the others. Larger monitors look as they did.
• Requirement lines: a material or a product specification from a description, such as the “PP”, “LEVEL INDICATOR” or 2" in LEVEL INDICATOR 2" SIDE FLANGE MOUNTED PP, is no longer saved as the line’s tag number. The line reads “Not provided” and the value stays with the line, under Also stated for this line (R102). Lines read before this change keep what they hold until the enquiry is read again or a person edits them.

2026-11-01

• Signing in: a Microsoft sign-in that has run out is renewed in the background on the next page you open, for up to 12 hours, so you are no longer sent to the sign-in page after a break. Where a screen has already noticed, the page banner and most screens say Session expired with Sign in again, which renews the sign-in and brings you back to the same page. When FlowOS refuses a sign-in it still holds, they say Sign-in no longer accepted with Sign out; when you are signed in to Microsoft but FlowOS has no account for you, they say No FlowOS account and to ask an administrator. A sign-in Microsoft refuses no longer bounces you back to Microsoft over and over; it stops at the signed-out page, which now says why. Those screens say You don’t have access to this when your role does not cover them, instead of a failure to load, and say when they cannot reach the server, with Retry.
• Requirement lines: a client’s answer filled into a line now counts as review work: processing the enquiry’s email again, which would discard it, needs permission to edit the enquiry. A line whose own words named no product family is looked at again once an answer fills it, and the enquiry’s draft quotations drop their stored total and ready-line count, here and when lines a client adds are gathered, so the lists show nothing stale until the draft is next opened. See Requirement gathering.
• Access: a role’s permissions show read-only to anyone who cannot edit roles, Enrol shared shows only to those who may enrol a shared mailbox, and a person’s Enrol, Pause and Resume mailbox controls show only to those who may enrol or change mailboxes. See Mailbox management.
• Quotations and line review: a value the client states that the product’s header does not list, quoted as that header’s Custom option (such as SCALE MOC CU worded Aluminium), is no longer called a deviation: the quotation, its PDF and line review drop “stated … not offered” for it, and it no longer counts against the product’s fit. Its price is typed in a new Custom option rate box on its option row; a row that affects the price keeps the line unpriced until a rate is typed (₹0 allowed), any other row adds nothing until one is, and the rate is part of the line’s unit price on the PDF. A withheld change names any Custom option rate it held. A header without Custom still marks the value not offered. See Business rules (R78).
• Dates: the dates on a person’s roles, office grants and access history, on a limitation, a sizing table, a rate, a revision request and a quotation’s comparison now show as they fall in India, such as 5 Jan 2026, whatever the browser’s own time zone.
• Quotations and Inbox: a revision request’s changes are now decided on the email: its panel lists them with Accept and Decline, then Start R1, Add to R1 draft or Open R1 draft. Accepted changes with one plain value are written into the revision: a line’s quantity, a line removed, a discount, the validity and the warranty; each change says Will set…, Applied to R1 or Edit by hand, also on the quotation. Accepting no longer leaves every edit to a person (R119). See Revision requests.
• Previews: a PDF preview zoomed wider than its pane now scrolls sideways, by trackpad or by the scrollbar shown along its foot on hover, in the inbox and on a PO check.
• Quotation: a revision’s PDF now lists Changes in this revision after its last line and ahead of the totals, naming the version issued before it by its printed number: the grand total before and after with the difference, each line changed (with each value it was and is now), added or left out, and the customer details, terms and charges that changed. Where a change came from stays on screen and is not printed. The original, the tag schedule and the datasheet print no such list. See Quotation builder.
• Inbox: the files a client attaches to a later email are sorted before they are read. A file the client already sent on the enquiry is passed over, so its comments are not counted twice. A table grading our offer (OK, NOT OK, Acceptable, Complied) becomes one review for a person, quoting the graded rows, and a picture attached as a file becomes one change for a person, “only in a picture”. Our own quotation sent back only names the version, and its comments are read as before. See Inbox.

2026-10-31

• Inbox: in the changes a client asks for before a quotation is issued, each enquiry line is now headed by the product the system suggests for it, such as Metal Tube Rotameter - 65NB, with its item code, instead of its product category.
• Inbox: in the changes a client asked for on an issued quotation, each line is now headed by the product that was quoted, such as Metal Tube Rotameter - 65NB, instead of its product category, such as Rotameters, with its item code beside it. A size change is shown against the size of the quoted product, struck through beside the size asked for, with the size the enquiry stated below it.

2026-10-30

• Requirement lines: a line a client adds in writing in a later email, before the quotation is issued, is now added to the enquiry’s requirements as a new line awaiting review, after the last line, under the product category its details point to, even one the enquiry had no lines of. The earlier lines and what was reviewed on them are left as they are, a datasheet the client sends again unchanged is not read a second time, a line the enquiry already holds, such as one in a forwarded original, is not added again, and the client’s changes show as applied only when that many lines were gathered with some detail on them; a product the catalogue does not have stays to confirm. See Business rules (R120).
• Inbox: an enquiry card shows Ordered once the client has signalled an order: a purchase order, a confirmation in their own words, a request for a proforma invoice, or a note that they will raise a purchase order. Changes the client asks for in later emails are then held for a person instead of being listed for the next revision. See Inbox.
• Quotations: the changes a client asks for after a quotation was issued are listed on the quotation under Revision requested, email by email, with the client’s words, the value we quoted and the value asked for, and a link to open the email. Someone who may edit the quotation can accept or decline each, and reopen it; accepting records the decision and marks the change for the next revision, which carries it, and does not edit the lines. A change whose email arrived after the quotation’s validity, or against an older revision, is marked, and one held after a purchase order shows why and has no decision. The quotation lists show Needs revision · n. See Revision requests (R118, R119).

2026-10-29

• Quotation: units print the way engineers write them, M3/HR as m³/h, KG/CM2 g as kg/cm²(g), Deg.C as °C, barg as bar(g), still in the customer’s own unit. A unit FlowOS does not recognise, such as LPH, prints as written. The flow a line asked for, shown on the product suggestion and in a deviation note, is spelled the same way (R87).
• Requirement lines and quotations: a flow meter or rotameter line that states a minimum and maximum flow but no normal flow now takes their mean as its operating flow, marked Calculated on the quotation and inferred on the line, the way pressure and temperature already did. Its quotation no longer prints Operating Flow as Not stated. The figure is shown only; sizing still reads the flow the enquiry states (R87).
• Quotation: a line’s operating conditions now follow its datasheet. Pressure, temperature and, on flow meters and rotameters, flow print as a grid with columns for minimum, operating, maximum and design, each figure in its own cell with its own mark, pressure first as on the datasheet, then the Flowtech Flow Range. The line’s other operating conditions follow in the datasheet’s order and under its labels. The fluid now prints as Service, as the datasheet names it, and the place or equipment the line serves as Application, where it was “Location”. A Flowtech flow range the enquiry gives only in words prints in that row, and a flow meter family with no Flowtech range of its own prints it as Not stated. Issued quotations keep the conditions they were issued with (R40, R87).
• Inbox: mail waiting in Needs Review is now shown to its own office and to whoever it is assigned to, as processed mail is, and on the conversation of an enquiry a person may read; until now only people who read across all offices saw it. An office head can open their office’s review mail, its attachments included, see why it waits, and link it or give it a type; a sales person can do the same for review mail assigned to them. Mail assigned to no office, and moving review mail to another office or owner, stay with people who read across all offices. The empty tab now says “Nothing waiting for review”. See Inbox and Roles.
• Client changes: every change a client asks for is now recorded with its email and a state from when the email arrived: held after a purchase order, on the revision list of an issued quotation, or to confirm. Before a quotation is issued, an answer to a question sent with Raise query fills the field it answers when that field is empty, with the reply as its source; it never replaces a value the team set or the client stated differently, and those answers wait for a person (R117).
• Inbox: a query sent with Raise query is now saved with its email: who sent it and when, and each question kept, with the line and the need it asks about, such as the flow rate of line 3. Asking a line about the same need again withdraws the earlier question, and a query left with no open question is closed. Nothing on screen shows saved queries yet; matching the client’s answers to them comes with client changes. See Inbox.
• Datasheets: every datasheet’s OPERATING CONDITIONS heading now opens with the same rows: Service, Minimum, Operating, Maximum and Design Pressure, the same four for temperature, and on flow meters and rotameters Minimum, Operating and Maximum Flow and Flowtech Flow Range. Rows that had been saved under shortened names, such as “Operatin” and “Maximum Tem”, and the older Op. Press and Op. Temp ranges, are now these rows, and values already read under the old names moved with them. Until now the assumed ranges and design values, the product checks and the quotation’s operating conditions missed what most families stated. A scale or calibrated range the client asks the meter to be supplied with now prints as the Flowtech range, marked Stated; a flowmeter’s stated flow range is read as its minimum and maximum flow, and a scale field holding the line’s own flow is read as that flow. An instrument’s own rating, such as a sight glass’s maximum pressure, is now a Rated Maximum row. See Datasheets and R65, R87 and R108 in Business rules.
• Requirement gathering: 432 datasheet headers across 36 families now carry a description of what they hold and what goes elsewhere, where they had none, one that contradicted their choices, or an editor’s note such as “Remove in PP”. Among them are headers that switch others on. Orifice Flange Assembly Details now says that flanges, WNRF or weld neck flanges, an orifice flange assembly or an orifice set mean Required, and the plate alone is the default; an orifice enquiry asking for weld neck flanges had every line read as a bare plate. The level transmitter and level switch headers on magnetic level indicators, and the isolation valves on transparent and tubular gauges, say the same of their parts. The minimum, operating, maximum and design pressure and temperature headers now say which is which. A description edited on the datasheet page since 29 October is left as it is. See Decodification.
• Inbox: a reply or query sent from FlowOS now starts with the enquiry’s office head in CC, so the client’s reply-all reaches a mailbox FlowOS reads: the enquiry’s assignee when they head its office, otherwise every head of its office, at their own mailbox where they have one. A line under CC says why, and the head can be taken out before sending. Nobody is added on an email to colleagues only, by a head to themselves, or on an email with no enquiry; CC holds at most 10 addresses and names any head it leaves out. See Inbox.
• Inbox: a test system can now send every email FlowOS sends, replies and queries alike, to one test mailbox instead of the people it is addressed to, so no client receives mail from it. The compose dialog then says Test mode and names that mailbox, and the conversation shows the email as sent there. Switching sending on now also means choosing between the test mailbox and delivery as addressed. See Inbox.

2026-10-28

• Requirement lines: a client’s material is matched to an option by the owner’s rulings. “MS” takes “CS ASTM A36 - Sheet”, the mild-steel grade, and stays Custom where the part offers only forged or cast carbon steel such as A105. “Hastelloy C” no longer takes Hastelloy C-22, a different grade. A part whose only option names the client’s material takes it, so gland packing “PTFE” takes “PTFE + Neoprene”. See R76 in Business rules.

• Product suggestions: on a plastic line, a bare process connection size that is a standard plastic pipe outside diameter is now read as that pipe’s nominal bore, as the main line size already was: HDPE 225 is sized at 200 NB, PPH 180 at 150 NB and PPH 90 at 80 NB. A rotameter’s line size usually lands in its process connection size, so these lines were sized one size up. See R94 in Business rules.

• Requirement gathering: a long table no longer loses a column on one block of ten lines when the other blocks wrote it joined with another column, such as “200 NB; 193.7 mm” for pipe size and pipe bore. On one local orifice enquiry of 36 lines, lines 11–20 now keep their stated pipe size, so they can be sized. See R72 in Business rules.

• Product suggestion and menus: a size written in inches is now read wherever it appears.

  • A size field holding 1-1/2”, 1½″, 2 in or 8 inch is read as its nominal bore on the pipe table (40, 50 and 200 NB). Until now inch wording gave no size, so the line could not be sized from it.
  • A line with no size field reads an inch size from its own text, such as “LINE SIZE: 8”” in a BOQ row. Text naming two different sizes, such as “Line Size: 4”; Drain: DN15”, now gives none, where it used to take the 15.
  • In menus, 1/2” NPT, 1/2” NPT, 1/2″ NPT, 1/2’’ NPT, 1/2 inch NPT and ½” NPT compare the same.

  See R29 in Business rules.

• Requirement gathering: a value the reading left out of every field now goes into the one field its column names, by one of the field’s labels, when that field is empty, so a “Line Size: 50 NB” column fills the field labelled MAIN LINE SIZE instead of being listed as not placed. On a by-pass rotameter datasheet about one reading in four left the size out of some or all lines, and those lines then lacked the size product sizing needs. A column naming the item or its type, one naming no field or several, and a cell that only asks the vendor to specify are left as before, and so is a size the reading put into another field, such as the acrylic body rotameter’s process connection size. See R72 in Business rules.

• Purchase orders: FlowOS now reads a linked purchase order and compares it with the quotation version it accepts (R113). The PO check in the inbox shows the differences, where what a PO does not state is not a difference (R114), and the deemed-acceptance date when the PO has one (R115). A person with edit rights can re-match a line or the compared quotation, and an Office Head can record Accept, Accept with deviations or Ask for amendment, shown as “Check changed since” if the check moves (R116). Settling a row and editing a PO value are still not saved. See Checking a purchase order.

2026-10-27

• Inbox: a picture a client pastes into the text of a later email, such as a screenshot of a revised table, is now read for the changes it asks for. Until now the change reader read only the typed lines around it, so Changes asked for could say the client asked for nothing. The picture reader transcribes it, its text joins the client’s sentences where the picture sat, and a change read only from it says “only in a picture”. At most five pictures are read per email, icons and small logos are passed over, and a picture that could not be read, is over 512 KB, or may not be sent, is named in the “Could not read” line, such as “Image 2 in the email body”. It applies to client mail read afterwards. See Inbox and Limitations.
• Requirement lines and quotations: assumed pressure and temperature now follow Flowtech’s practice. An enquiry that says ATM, or gives no pressure, on a liquid line is taken as 1 bar g over 1–3 bar g with a 3.9 bar g design, unless the line is vacuum service; ambient temperature is 40 °C over 28–52 °C with a 67.6 °C design. Everywhere else the range is 30% either side and the design value 1.3 times the maximum, with no minimum width or margin, so a stated 44 °C maximum is designed for 57.2 °C, not 69 °C. The line shows the same assumed figures the quotation prints, where until now the range and design of an ambient line appeared only on the quotation, and an ambient pressure printed as −0.5 to 0.5 bar g. An assumed range end or design value above a product’s limit is noted on the product but no longer warns or moves it down the order, so a 98 °C line keeps the electromagnetic flowmeter rated to 100 °C. The boiling and cavitation checks still read an assumed pressure as atmospheric. See R17, R24, R65, R68 and R87 in Business rules.
• Requirement gathering: a menu that only says whether a part is fitted, such as switch details (Required or Not Applicable), a level transmitter, an isolation valve (With or Without) or IBR (IBR Approved & Certified or Non-IBR Certified), now takes the fitted option when the enquiry describes the part instead of writing “required”, as “Contact type NO/NC; 3 switches; low level 300 mm”, with that wording kept as the value’s note, and the other option when it says “Not required”, “NA” or “Non-IBR”. Until now such wording took no option, so the quote printed the default, often Not Applicable, and a priced part dropped off it. Wording that leaves the part conditional or open, such as “if required” or “as per datasheet”, is still put to the reading model. The reading also keeps the details of such a part, such as a switch count or set points, on its menu, where it could list them under Also stated for this line instead. It applies to enquiries read afterwards. See R76 in Business rules.
• Requirement lines: a line whose remarks or status column says only that the client deleted it, put it on hold or has it supplied by others, such as “Deleted”, “Confirmation pending from client hence it is on hold” or “Vendors scope”, now arrives excluded automatically with the client’s words as its reason, such as “Client: Deleted”, and the quotation skips it. Until now such lines were read as ordinary lines with product suggestions, left in review. A remark that says more, such as “Changed type to vortex, by client”, leaves the line in review, and confirming an excluded line reopens it. Applies to enquiries read afterwards. See R112 in Business rules and Line items.
• Inbox: a board card brought back to New by mail on its conversations now says what came in, such as “New revision requested”, “New purchase order” or “New follow-up”, where it gave the bare type (“Revision request”); several unopened emails read “3 new · latest revision request”. A copy of a client email already held (R2a), which has no type of its own, now takes that email’s type, including one a person corrected when linking it, so its card no longer reads “New email”. See Inbox.
• Inbox: a purchase order’s panel now shows how the PO check will read, on a made-up sample PO under a banner saying so: each line, party and term compared with the quotation, differences first and matches folded, which rows hold up the order (proposed rules, pending Flowtech), and Sales Order generation locked until they are settled. Source shows the quotation and the PO document side by side, and each row can be corrected or settled from its ⋯ menu. FlowOS does not read purchase orders yet, so nothing on the sample is saved. See Inbox.
• Quotations: a revision now marks what changed since the version issued before it. Each changed line value shows the earlier value struck through above the new one, with where the change came from when FlowOS knows (edited on the draft, changed on the enquiry line, or a price that followed the line); added lines are shaded, lines left out are listed with the amount they take off, unchanged lines fold, and a strip gives the counts and the grand total before and after. The customer, terms and charges cards list their changed fields. The PDF is unmarked. See Quotation builder.
• Requirement gathering: values a document lists under particular lines’ item codes or tag numbers, such as a data sheet column headed by two lines’ codes, now reach the lines with those codes even where the reading first gave them to other lines, for instance by matching their descriptions. Each line they were moved onto or off is held for a person with a Placed by code note, citing the passage that names the codes, to check against the document (R70, R71). See Business rules.
• Reading documents: the picture reader no longer guesses at a scan or picture it cannot read clearly. It copies spelling and brand names as printed and writes [illegible] where a word or number is unsure. Until now it could write a plausible value in its place, such as 0-4 V for 0-5 V, a common steel grade for the printed one, or another brand’s name, and requirement reading took that as the line’s value. A value marked [illegible] is now read from the attached file, or left unstated when the file does not show it clearly. Documents transcribed before this change keep their transcription. See Reading documents and Requirement gathering.
• Mail processing: an email a client sent that FlowOS types as a quotation or a sales order, kinds only Flowtech sends, now waits in Needs Review with the reason “FlowOS can’t tell what type of email this is”, instead of being filed as one of ours unread. An RFQ that also carried an earlier Flowtech offer was filed that way, and its scanned documents were never read. Once a person picks Enquiry with Reclassify, it is processed afresh and its documents are read. See R7 in Business rules.
• Inbox: Changes asked for offers All lines again whenever FlowOS knows the whole list of lines, on a FlowOS quote or when the changes are matched to the enquiry’s lines. It lists every line, and the lines nobody asked to change come last under No change asked, muted, each opening with the enquiry’s values and nothing asked. Changed, New and To look at, and the summary’s counts, leave them out. See Inbox.
• Inbox: in Changes asked for, the page beside a changed line, such as “p.7 ↗”, now opens the marked-up quote at that page in a new tab. The opened line lists only its operating conditions and technical or design specifications under the changes, with the values the enquiry states once for every line, and a part with no change of its own shows its own enquiry line, or “Enquiry: —”, never another tag’s. A code no line holds can be picked as a part of its line, and the line’s tag count leaves it out. The inbox List shows the red “⚠ Link doubtful” chip beside a client whose enquiry has a doubtful link. See Inbox.
• Inbox: in Changes asked for, a code in a comment beside a quote line that no line holds, such as PT100 in “Temperature element PT100”, now shows on that line in a row of its own, with a note that it is on no line of the quote or the enquiry, instead of falling under Not matched to a line; it is not applied to that line’s tags. A tag written on two enquiry lines now reaches both, and a FlowOS quote version with no lines is passed over, so the summary no longer reads “No lines change” over lines from the enquiry (R111). See Inbox.

2026-10-26

• Reading documents: a typed PDF with some scanned pages, such as a typed RFQ with a scanned datasheet among its pages, no longer loses those pages. Until now the document reader could drop them without a trace, and a PDF it judged mostly scanned was sent whole to the picture reader, typed pages too. Now the typed pages keep their text, in page order, and the scanned pages are transcribed by the picture reader on the same terms as a scanned PDF, each run of them on its own. Until they are, the document shows a note such as “[Scanned pages 8–9 of “schedule.pdf” are not read.]” where they stand. See R50 in Business rules and Reading documents.
• Quotation: a glass tube, metal tube or acrylic body rotameter is now priced from the band that holds the top of its Flowtech range, read as water equivalent, and a top on the edge of two bands takes the lower one. Until now the band had to hold the client’s whole range as written, so a range starting at 0, a gas flow in Nm³/h, or a range crossing two bands left the line unpriced with “No price band covers the line’s flow range”. The cheaper-family ranking in product suggestion reads the band the same way. The metal tube rotameters’ price bands entered in m³/h are relabelled LPH, the unit of their price list. See Pricing and totals and R28 in Business rules.
• Inbox: the changes a client asks for now show line by line, in a Changes asked for column in place of the amber card. Each changed line shows the value asked for beside the value we quoted, struck through, and the enquiry’s own value with a chip: as enquired when the client asks for what the enquiry already said, new ask when it did not. A line splits when its tags ask for different things; a change applies only to the tags the client named (R111). Clicking a line opens it beside the column, with the client’s sentences and links to the marked-up quote and the enquiry. Nothing is applied yet. See Inbox.
• Inbox: every email linked to an enquiry is now checked against it, whatever its type, and one that may belong elsewhere is flagged: a red banner at the top of its action column with the product, tag, quote, project and client comparison, a “⚠ doubtful” chip in the mail summary, and a “⚠ Link doubtful” chip on the enquiry’s card. Mail that is only partly outside the enquiry gets an amber note in the action column. It belongs here confirms the link and Change link moves it; a confirmation is recorded in the email’s history and also settles the email’s copies. A different client alone makes an email doubtful only when nothing strong agrees (R110). See Inbox.
• Product suggestion: a line, its document or the enquiry’s subject or body that says “Non-IBR”, “IBR: No”, “IBR not required” or “IBR as applicable” no longer names the IBR vortex flowmeter, so “Non-IBR vortex flowmeter” stays the vortex flowmeter, and “IBR approved vortex flowmeter” still names the IBR one. It applies to enquiries read afterwards. See R27 in Business rules and Product suggestion.
• Product suggestion: these apply at once, on every line without a reviewer’s pick, when the data reaches a database: which families are suggested on demand, the IBR vortex flowmeter on a steam line that is not condensate and sized on the vortex flowmeter’s flow tables, the electromagnetic flowmeter leading on conductive liquids when the client names no type, and the smart and the miniature pressure transmitters’ ranges starting at -1 bar. The IBR vortex flowmeter is suggested only on such a steam line or when the email asks for IBR; the miniature and the differential pressure transmitters only when a line asks for them, and “pressure transmitter” alone no longer brings in the miniature. The words that ask for a family (IBR anywhere in the email; mini, miniature, pencil; DPT) count for enquiries read afterwards. A line that said “pencil” or “DPT”, or whose email said IBR, shows the miniature, the differential pressure transmitter or the IBR vortex flowmeter again once its enquiry is processed again. See R27 in Business rules and Product limitations.
• Product limitations: a family’s page now sets When FlowOS suggests it: whenever it fits the line, or only on demand, when the enquiry asks for it, with the words that ask for it. A word can ask for the family wherever the email says it. The family’s own name always counts, and the words FlowOS knows already are shown read-only. The choice applies at once; changes to the words apply to enquiries read afterwards. See Product limitations.
• Product suggestion: a family with one item code, such as the radar and ultrasonic level transmitters, is now always offered with that code; its size field is set on the line. Until now some read “sizing not available” or “can’t size yet”. See R29 in Business rules.
• Inbox: right-click a board card to assign its enquiry without opening it, to yourself or to anyone active in an office. It is offered to people who may reassign mail; unassigning stays on the open email. See Inbox.
• Inbox: each board card now leads with a strip saying what is next: the newest unread mail in New, “Review 3 of 8 lines” in To review, and “✓ Ready to quote · 6 lines” in Ready to quote. The client’s RFQ number sits beside the client, the owner shows as initials, and the product categories have moved off the card to the enquiry’s reading. See Inbox.
• Inbox: a Board | List switch on the Active tab shows every enquiry as one table, sortable by client, stage, first email received and due date, paged, and following the board’s search and assignment filter. See Inbox.
• Inbox: the board’s search now finds an enquiry by its client’s name, as the card shows it, by the client’s RFQ or reference number, and by a quotation number, as well as by subject and sender. Clicking into the empty search box lists the enquiries you opened most recently and the column each is in now, and typing lists the enquiries the search finds; picking one opens it. Back on the board, the card you opened last is outlined wherever it now sits. See Inbox.
• Requirement gathering: a flow written as minimum, normal and maximum figures, such as “10/700/900 Min/Nor/Max”, now keeps its stated maximum when the reading saved only the minimum and normal flow. Until now the line showed a maximum worked out from the normal flow, marked as not stated, and the quote printed it. See Line items.
• Office routing: when FlowOS routes an enquiry to an office after its lines were read, as when a later email resolves the client’s State, the enquiry’s lines and the changes the client asked for now move to that office with it. Until now they stayed where they were: with no office, visible to every office, or with the earlier office, out of sight of the new one. See Automatic behaviour.
• Inbox: the clock button beside an email’s assignment line opens its Email history: each time it was linked to an enquiry, moved to another or unlinked, each time its type changed, and each time its office or owner changed, oldest first, with when, who made the change (FlowOS for linking and routing, or the person who relinked, reclassified or reassigned it), from and to, and why. Changes are recorded from this release; earlier changes were not kept. See Inbox.
• Product suggestion: among families that fit, a family the line matches on any one of its ideal uses now ranks higher; until now it had to match all of them. The more accurate family, then the cheaper one, now come before how much of the line could be checked. Accuracy is read from Flowtech’s guide: 0.5% of the measured value for the electromagnetic flowmeter and 1.0% for the vortex and turbine; a full-scale accuracy, as on the rotameters, counts at the line’s operating flow. Price is the item code’s base or price-band price. A family whose accuracy or price is not known ranks after one whose is. The product’s reasons say “it is more accurate” or “it costs less” when that decides. See R28 in Business rules and Product suggestion.

2026-10-25

• Mail processing: a client’s chaser in an enquiry’s conversation, such as “Waiting for your quotation” or “Please quote for the trailing mail”, now joins that enquiry as a follow-up. It used to wait in Needs Review as “No product Flowtech sells was found in it”, unlinked, because it names no product. An email naming no product, with no enquiry in its conversation, still waits there. See R8 in Business rules.
• Mail processing: an email FlowOS cannot tell the type of, such as a purchase order or a follow-up it is not sure about, no longer becomes an enquiry. It waits in Needs Review with the reason “FlowOS can’t tell what type of email this is”, its type showing FlowOS’s best guess, and nothing in it is read. One that links by our quotation number is linked as before. Emails already read before this change are unchanged. See R7 in Business rules.
• Inbox: Reclassify now works on an email waiting in Needs Review: pick its type and FlowOS processes it again as that type, without asking the classifier again. It is offered to people who may edit the inbox, and only in Needs Review. See Inbox.
• Sign-in: pressing Back after signing in no longer shows the sign-in page. Someone already signed in who reaches it goes straight on to the screen they were opening, or to the dashboard. After sign-in FlowOS now opens only its own pages, whatever return address the sign-in link carried.
• Rail: every section of the left rail, such as Master or Sales Quotations, now starts open; clicking a section’s heading still folds it for the rest of the session.
• Inbox on a phone: the board shows one column at a time, chosen from a row of chips with their counts, To review first. Below 1024 pixels wide, as on a phone, a tablet or a zoomed-in laptop, an open conversation shows as two tabs, Email and Lines, where until now the lines and their actions were left out entirely. The Lines tab opens on the lines awaiting review, with Review next at its foot and the other actions behind More. See Inbox.
• Inbox: opening a card now gives the conversation the whole page: the board’s title bar, and its tabs, assignment filter and search, stay on the board. The email list folds to a narrow strip of tiles, one per email, each with the sender’s initials, a dot in the colour of the email’s type and a crimson dot while it is unopened; hovering a tile shows the email’s type, sender, subject, date, due date and attachments. FlowOS remembers in this browser whether the list was folded. See Inbox.
• Dark theme: the top bar has a theme menu that switches FlowOS between Light, Dark and Match system, kept in each browser. Light stays the default. An email’s body is shown light on dark, and the quotation preview stays on a white page. See First sign-in.
• Top bar: the top bar now shows where you are, such as Master › Item Master, in place of the line above each screen’s title; on a screen opened from a list, the list’s name links back to it. The menu under your avatar holds Preview as, the theme, density and Sign out, and while a preview is on, the bar names the person being previewed beside a Stop button. The bar fits at every window width, a phone’s and a zoomed-in laptop’s included. On a phone it shows the screen’s name, the unit converter and your avatar, and density is left out. See First sign-in.
• Home: FlowOS now opens on the Global Inbox, and signing in lands there unless you were on your way to another screen. Someone who cannot see the inbox lands on the Dashboard, which keeps its place on the rail. See First sign-in.

2026-10-24

• Mail processing: when the same client email arrives twice and the later one is read first, as after a mailbox is synced again newest first, the earlier one is now the one kept and read, and the later one becomes its copy, as long as the later one has not been typed yet and adds nothing to the earlier one. Until now the earlier email became the copy, was never typed, showed as “Not classified yet” and sat on no enquiry. A copy now joins the enquiry the email it copies is on, taking that enquiry’s office and owner unless it was reassigned by hand, and its type reads “Copy of the 1 Oct email”, linked to that email. Copies already held join their enquiries once the data fix runs. When fetched earlier mail holds no enquiry email, the oldest client email that is not a copy starts the enquiry. See R2a in Business rules.
• Inbox: a client’s revision request or follow-up now lists each change it asks for, grouped by item, with the sentence it came from; What changed shows the enquiry’s mail email by email. Read-only for now: nothing is applied. See Inbox.
• Requirement gathering and line review: a pipe size written as an outside diameter, such as “101.6 OD” or “114.3 mm OD”, is now read as its nominal bore, from steel pipe diameters (ASME B36.10 / EN 10220 / IS 1239, 21.3 to 610 mm), hygienic tube diameters sized in inches (25.4 to 152.4 mm) and the plastic pipe diameters of R94. The size stays as written with the nominal bore beside it, so the line is sized at it; until now it was flagged as an incompatible unit. 101.6 reads as 100 NB, a 4 inch tube, with 90 NB, a 3½ inch steel pipe, noted in its formula. A diameter in none of the series is still flagged. Lines gathered earlier keep their flagged size until the enquiry is gathered again. See R106 and R94 in Business rules and the Glossary.
• Unit converter: a new Pipe size quantity shows a size in NB, inch and outside diameter, as steel pipe and as hygienic tube, from the standard tables. 101.6 OD is 100 NB and 4 inch, and 50 NB is 2 inch, 60.3 OD steel and 50.8 OD tube. A figure in inches is shown both ways: 2 inch as a length, 50.8 mm, and as a pipe size, 50 NB. A fraction such as 1-1/2" is read as 1.5 inch. On the line review, the unit menu of a size box in NB now lists pipe sizes. See First sign-in.
• Requirement gathering: a flow written as figures with no unit, such as “4/35/50 Min/Nor/Max Flow”, is now saved as figures where it was kept as text. It takes the unit every other flow line of the same email and category states, whatever its letter case and provided it is a flow rate, marked assumed; otherwise it stays without a unit and a quotation prints “(unit not stated)” beside it. Min/Nom/Max reads like Min/Nor/Max. Order words written beside figures, such as Min/Nor/Max or Min/Max, now order them as a column heading does, for pressures and temperatures too, and a flow range written in words with its unit is read into numbers like a pressure. Lines gathered before keep their text until the enquiry is gathered again. See R107 in Business rules and Line items.
• Product suggestion: an electromagnetic, vortex, turbine or oval gear flowmeter on a liquid line that states its size but no usable flow (none, figures with no unit, or a unit FlowOS cannot read) is now sized at that size, with its item code and the range that size measures, noted “sized on the stated 100 NB; flow not checked”. The line is no longer asked for the flow, and with nothing else open it is confirmed without a person (R71). The glass tube, metal tube and acrylic body rotameters, and gas and steam lines, still need a flow. See R28 and R29 in Business rules.
• Quotation: a flow meter or rotameter line now prints a Flowtech Range row after its minimum and maximum flow, and no design flow: the chosen size’s range for electromagnetic, vortex, turbine and oval gear meters, marked Suggested where the meter was sized on the client’s stated size, a tenth of the maximum to the maximum for rotameters, and the client’s own range for bypass rotameters and orifice. Flow figures given without a unit print “(unit not stated)”, a unit taken from the enquiry’s other flow lines prints Assumed, and the notes say so, ask the client to confirm a Suggested range, and say when the client’s minimum is below what the meter measures. Issued quotations are unchanged. See R87 and R108 in Business rules.
• Line review and product suggestion: a density written in a gravity field, such as 850 in a Sp.Gr / Density row, is no longer read as 850 times the density of water when a person saves a flow in review or a product is suggested: a figure of 20 or more there is a density in kg/m³. A gas or steam line’s specific gravity written with no unit, which is against air, is no longer read as a density at all, and on a line whose gas is only assumed from its name a gravity under 20 is read against water with a caution. Gathering an enquiry is unchanged. See R109 in Business rules.
• Requirement gathering: a liquid’s flow given by mass, such as 2,994 kg/h, now converts with the specific gravity its line states without a unit, such as 1.5 in its Sp.Gr / Density row, read against water at 998 kg/m³ (2 m³/h), as the product suggestion already read it. Until now only a density in kg/m³ or the fluid library’s was used, so a line on a fluid the library does not hold stayed unconverted. A stated density still comes first and the library’s last, and the conversion’s information mark shows the density worked out and the water it was read against. A figure under 20 written in kg/m³ on a liquid line, a specific gravity under the wrong unit, is no longer taken as the line’s density. Existing enquiries change when next gathered. See R109 in Business rules and Requirement gathering.
• Product suggestion: the bypass glass and metal tube rotameters are no longer suggested on a line that does not name them, except as the glass tube rotameter’s fallback: they are listed when the line’s flow is above every glass tube’s range, since a bypass rotameter is made to the client’s flow. A line that asks for a bypass rotameter by name still lists it. A glass tube rotameter named for a flow above every tube’s range is cautioned, not ruled out (its sizing basis is marked assumed), and stays the pick; the bypass glass and bypass metal tubes are listed beside it and rank as R28 says. Only when the glass tube is ruled out does R88’s try-next order put the bypass glass, then the bypass metal tube first. See R27 and R88 in Business rules and Product suggestion.
• Item Master: the ten largest electromagnetic flowmeter codes, 550 NB to 2200 NB, now show their measuring range, and the 15 NB metal tube rotameter’s minimum reads 0.0025 m³/h (2.5 LPH), the figure its sizing row already used. The IBR vortex flowmeter codes stay in their own family when the item codes are rebuilt from Flowtech’s item master. See Item Master.
• Line review and quotations: a line the enquiry gives no tag number for, but which carries the customer’s own item or material code in its row, such as “Item Code: BO-61-0028”, is now known by that code. It heads the line’s review, its badge in the list of lines and its column in the comparison matrix, and the quotation, tag schedule and datasheet print it under Tag No. in place of “Not provided”. A line with a tag still shows its tag. A tag that a product’s datasheet keeps under a numbered Tag No. row, as on the oval gear and insertion ultrasonic flowmeters and the ultrasonic level transmitter, now shows too, where until now it read “Not provided”. On local data the ten lines of an enquiry listing only item codes, and one line of an enquiry listing material codes, gain their codes. See R102 in Business rules and the Glossary.
• Inbox: mail waiting for a link now suggests enquiries even when FlowOS matched none: after the matches it weighed, up to five other enquiries the same client started, marked Same client for the same address or Same company for another address at the same company. A webmail address suggests only its own enquiries, and a lead portal’s suggests none. Every enquiry, suggested or found by search, has one Link that says what it links as: the quotation FlowOS matched, else the newest quotation issued before the email, else Quote not in FlowOS when the email cites a Q/T quote number or is a purchase order or revision request, else no quotation yet; the menu beside it offers the others. The reason the email waits now reads on one line with “Not linked”. See Linking mail after a quotation and R105.

2026-10-23

• Inbox: mail citing an ERP quote number, such as T00126 or R3-T00126, now links to the enquiry whose other mail carries that number, marked Quote not in FlowOS. A number carried on mail of several enquiries sends it to Needs Review to choose. Linking one such email by hand, or earlier mail FlowOS fetched, teaches FlowOS the number for the mail after it. R97 gains this as its sixth step, after the same conversation and before the customer’s reference. See Linking mail after a quotation.
• Inbox: a client’s revision request, purchase order or follow-up that FlowOS cannot link now has its earlier mail fetched, where this is turned on. FlowOS looks for the earlier emails it names, up to 50, in every folder of the mailboxes it arrived in, Sent Items included. It reads what it finds oldest first: an enquiry email among it, or else the oldest client email, starts the enquiry, and our own quotation email joins it, marking later mail Quote not in FlowOS by its Q or T number. Then it links the email again. Earlier mail never waits in Needs Review, is never read for changes, and does not count as unread on the board. The email’s mail summary says what FlowOS found, such as “Fetched 5 of its 9 earlier emails from this mailbox”. See Linking mail after a quotation.
• Inbox: an email after a quotation now shows, in its mail summary, how it is linked: the enquiry, the quotation number or Quote not in FlowOS, and what the link rests on, such as “reply to our quotation email”. Mail waiting in Needs Review says why in plain words, lists the matches FlowOS weighed, and can be linked by hand to an enquiry found by subject, client address, customer reference or quote number, with one of its quotations, as Quote not in FlowOS, or with no quotation yet; linked mail can be moved with Change link. A linked email leaves Needs Review and takes the enquiry’s office and owner, and a client’s revision request, purchase order, follow-up or later enquiry email is read again within five minutes; FlowOS never changes a person’s link (R105). A type the link corrected, such as an enquiry email read as a revision request, is now shown everywhere in place of the classifier’s, and a card stays on its enquiry’s own email when later mail is linked to it. R8 now says how mail joins an enquiry. See Linking mail after a quotation.
• Fluid library: sodium chlorite (31%) now has corrosion grades for 13 more materials, from makers’ resistance charts and the OxyChem sodium chlorite handbook, each at the worst grade its sources give: carbon steel, SS 304, SS 316, SS 316L, polypropylene and neoprene D, aluminium C, Hastelloy C and FRP B, and PVDF, titanium, PFA and acrylic A; PTFE stays B and PVC D. A wetted part an enquiry leaves blank on a sodium chlorite line now takes a material these grades allow (R79), and a metal tube rotameter on it is lined with PTFE (R89). Copper and tantalum have no grade yet. See Business rules.

2026-10-22

• Business rules: R65 and R68 now name every unit their minimums apply in. R65’s assumed range keeps at least 10 °C, 0.5 bar or 0.5 kg/cm² either side, and in another unit, such as °F or psi, is 30% either side alone. R68’s design floor also covers kPa, MPa and kelvin, and in another unit, such as mmWC, the design value is 1.3 times the maximum alone. FlowOS already worked this way; only the text changed. Item groups now describes the Suggested prefix offered when an item group is added.
• Product suggestion: a product sized by one of its options, such as a smart pressure transmitter by its pressure range or a clamp-on ultrasonic flowmeter by its sensor size, now takes the released item code made for that option, else the product’s only code, which covers its whole range with the chosen option in its model number, so its line can be confirmed. An option neither gives a code for is still chosen and says “no released item code for this option”; that line still needs a size before it can be confirmed. On local data a smart pressure transmitter line on its 0 to 10 bar range and a clamp-on flowmeter line on its small sensor (15 to 100 NB) gain their item codes; the displacer level switch has no released codes, so its lines are unchanged. See R29 in Business rules.
• Product limitations: the level switches’ smallest process connections are as Flowtech gives them: 40 NB for the side mounted switch, where the product limitations guide said 50 NB, 25 NB for the top mounted switch, which had none, and 50 NB for the displacer switch, as before. A line on a smaller connection rules the switch out. On local data no switch line changes its suggestion. See Product limitations.
• Product suggestion: the side and top mounted level switches are now sized by their process connection size, as their datasheets’ float sizes say: the side mounted switch takes the 36 × 100 float for a 40 NB flange and the 48 × 100 float for 50 to 80 NB; the top mounted switch takes the 25 × 25 float and 10 mm float pipe for 25 to 40 NB, and the 48 × 48 float and 14 mm float pipe for 50 to 80 NB, so its model number no longer misses the float pipe. Neither shows “Sizing not available” any more. A line on any other size rules it out. On local data three side mounted switch lines on 50 NB flanges take the 48 × 100 float; a fourth, written “NB 150#” with no bore, asks for its size. See R29 in Business rules.
• Requirement gathering: a row that gives each of its variants its own count, such as a level switch row of 9 reading “LENGTH:-400 MM LONG(03 NOS) & 600 MM LONG(06 NOS)”, is now read as one line per variant in the row’s place: 400 mm long × 3 and 600 mm long × 6. Lines read from one row that carry the same tag are each marked “Duplicate tag” for a person to settle, even a tag with no digit such as “LS”; a tag with no digit repeated on separate rows is still not one. On local data this row is the only one of 356 that splits. A line confirmed while it still holds its Duplicate tag mark prints “Tag LS is listed on more than one line of the enquiry.” among its notes on the quotation, under a Duplicate label. See R73 and R95 in Business rules and Quotation builder.
• Requirement gathering: an enquiry is no longer left ungathered when the reading model skips one of its documents. On an enquiry with two datasheets the model answered for only one of them in about one reading in three, and the whole reading failed. The skipped document is now asked for once more by name, including a PDF or image read from its file and a schedule of one row, and its text is kept with the enquiry if it is still left out. See Requirement gathering.
• Requirement gathering: lines read from one datasheet column that lists their tags together, such as a total quantity of 2 with tags FT-101 / FT-102, now take one tag each. Until now the reading could give both lines both tags, so neither matched the customer’s own tag list.
• Requirement comparison: each line’s column in the comparison matrix and Compare with Source is headed by the line’s tag number, such as 90GTF30CF501, or, for a line with no tag, by the customer’s own serial number as their datasheet heads it, such as “S.No. 3”. Only a line with neither still reads “Line 4”. The row beneath gives the quantity and the rest of the customer’s row, without the serial and tag already shown above it. The line’s review state is a coloured dot beside the heading at every width, named when pointed at, so a long state no longer hides the tag. In the list of lines, each line shows the same tag or serial number as a badge before its category, and the line review’s header shows the serial number where the line has no tag. See Line items.
• Line review: the line review reads by colour. Each value in the header’s band is a tile tinted by where it came from: green where the enquiry states it, blue-grey where it was worked out, amber where it was assumed, violet while the customer is still to be asked, and grey otherwise, as the datasheet marks the same origins. The four groups of open items are tinted cards in their colours, and neither they nor the cards in the list of lines are ruled down their left edge any more; and Ask the customer is now violet, on its cards and dots alike, where it was black. The review state is a filled badge, an assumed quantity carries an amber tag, the product strip is white, and the datasheet’s fold shows its fields by origin as a bar with coloured counts. Also stated for this line and Other passages show their counts as badges. See Line items.
• Requirement gathering: no line is confirmed as it is gathered any more; every line is saved awaiting review, except one whose item Flowtech does not make, which is saved excluded as before. A line is confirmed without a person only once its product suggestion is read and its fluid is settled, its product fits with a size and nothing holds it. Lines confirmed before this stay confirmed. See R71.
• Roles: the Sales person role confirms and excludes the lines of the enquiries assigned to them, so the person assigned an enquiry reviews its lines and generates its quotation. An office head still can, for the office’s enquiries, and follows their progress. See Roles.
• Line review: a line can be confirmed only with a settled fluid, a product and a size. The fluid is settled when it is a library fluid the reading matched or a person chose, or a name a person recorded for a fluid the library does not hold; a guessed fluid, the customer’s wording the library does not hold and no fluid are not. Confirming without them is refused, saying what the line still needs; excluding is not, and Raise query still asks the customer. A line is confirmed automatically from its product suggestion only on the same terms. See R75, R81 and R71 in Business rules.
• Quotations: a quotation is generated only once every line it covers is confirmed or excluded in line review; a project’s quotation counts that project’s lines. Generating it otherwise is refused, saying how many lines still need review. A line that returns to review after its quotation was generated is still quoted, with its warning. See R38.
• Line review and inbox: Confirm is unavailable while a line lacks a settled fluid, a product or a size, and the status beside it says what the line still needs, such as “Needs a settled fluid before it can be confirmed.”; a change counts once it is saved. Generate quotation, and each of its per-project choices, is unavailable while a line it covers still needs review, saying how many, such as “3 lines still need review”. See Line items and Quotation builder.
• Line review: a fluid written as a chemical formula the library cannot match, such as “NaClO2” or “HCl + NaClO2”, is now named while requirements are gathered. A compound the library holds becomes a guess, and the fluid card says the formula it was named from. A mixture, a reaction or a compound the library lacks lists the chemicals it names, a reaction’s reactants and the product it makes, for the reviewer to pick: a library chemical sets the line’s fluid, one it lacks records it by name or, for a person who may add substances, adds it to the library with its formula. Only the formulas and their joins are sent to the reading model, each wording once. See Line items.
• Line review and quotations: a line that states its temperature or pressure under another name its datasheet gives it, such as Maximum Temperature on the float and board level gauge, is no longer also given an assumed ambient value. Until now only seven names for each counted, so such a line was assumed at 40 °C or atmospheric pressure, and its quotation printed an assumed range and design value beside the stated maximum. Every row the row library marks as an operating temperature or pressure now counts. See R17 and Setting up catalogue data.

2026-10-21

• Line review: an enquiry’s lines are listed and numbered in the order the customer listed them, whatever the instrument: the email first, then each attachment in the order it was attached, each in its own order, within each project. An enquiry mixing flowmeters and level instruments no longer lists all its flowmeters first, and a line with something open stays in its place, marked N open, instead of moving to the top. An instrument listed in two documents takes the place of its earlier listing. Draft quotations follow the same order; an issued quotation keeps its own. See R74.
• Line review: a person who may add substances adds a line’s fluid to the fluid library from the fluid card with Add to fluid library, on a line whose fluid is guessed, not in the library, or recorded by name. The short form asks for the fluid’s name, its phase, the customer’s wording, kept as an alias, and only the properties the line’s suggested product checks: density and viscosity, whether it conducts at 5 µS/cm or more, or its dielectric constant; with no product suggested, density and viscosity. Each opens with what the enquiry states, and a liquid’s density and specific gravity must agree within 1%. Saving sets the line to the new fluid; where the line cannot be set, the fluid stays added and the form retries setting the line only. Such a fluid has no corrosion grades until they are entered on the Substance Master, so its materials can’t be checked until then. The fluid search now finds an alias whatever its case or the spaces around it. See R67 and Line items.
• Roles: the Substance Master has its own view, add, edit and remove permissions, apart from the Item Master’s. Every role and exception that held the Item Master’s keeps the same access to the fluid library. See Roles and access.
• Client mail: mail from a client that is linked to an enquiry is read for what it asks to change, and the reading is listed on Mail Debug under Client changes. Comments typed onto a PDF the client attaches, such as our quotation sent back, are read too and pinned to the line and row they point at; a hand-drawn mark with no words is listed for a person. Nothing is applied to the lines yet, mail outside the test mailbox is read by keyword alone, mail to the test mailbox waits while model calls are off, and purchase orders still wait. See Limitations.
• Quotations per project: an enquiry whose lines are under two or more projects generates one quotation per project, one for a chosen project, or one of every line. Each project quotation holds only its project’s lines and prints its project highlighted at the top; the quotation card lists all of the enquiry’s quotations and downloads every project’s quotation, tag schedule and datasheet as one PDF. In the requirements, Move lines… beside a project’s heading moves lines under another project, and lines under no project must be moved before quotations are generated per project. See R74.
• Quotation: a quotation no longer has an application of its own. The quotation header no longer asks for one, and the strip under BILL TO no longer prints “Application: Not stated”; it carries the customer’s reference only, when there is one. Each line still prints its own application, type and location. See R40.
• Line review: a stated value the product filled itself, with its nearest option, its default or a rule, or as Custom, is no longer listed under Differs from the enquiry with Offer or Keep as written to click: the value stands, and its datasheet row still says what the customer wrote and that the product does not offer it. Only a stated value the product has no option for is listed, with the menu to choose one. See R81.

2026-10-20

• Product suggestion: the orifice plate and the ORF flange assembly are suggested only when the enquiry names them, as the ultrasonic flowmeters already are. A line asking for another flowmeter, or for none, no longer lists them. See R27.
• Line review: a value the enquiry states that the product’s menu does not list, on a menu with no Custom option, takes the product’s own choice, its default or a rule, so the line has an order code; it stays marked not offered and is printed in the quotation’s notes, as “stated 4-Wire not offered” on a vortex flowmeter. A line no longer waits for Offer on a value the product filled with its default or a rule over the customer’s wording: it confirms itself, as it does for a closest option. A listed value that a limit, rule or the size rules out still waits for a person. See R71 and R78.
• Quotation PDF: the quotation follows Flowtech’s format. BILL TO holds only the customer, its address, GSTIN, place of supply and contacts, with the application and the customer’s reference in a strip under it; a draft with no billing address reads “Address not given” and cannot be issued. Each line opens with its Tag No. (“Not provided” when the enquiry gives none), its application (the fluid) with its type and location. Technical specifications print no prices, two options to a row. Design specifications print only for the rotameter, bypass rotameter and orifice families. The amounts table has a % column (N/A where none applies) and a transportation row; payment terms show each stage’s amount of the grand total. The free-text Transportation clause is taken off the terms template. See R38, R40, R42 and R101–R103 in Business rules and Quotation builder.
• Mail debug: mail from a client that is linked to an enquiry is queued for its next step: later enquiry emails, revision requests and follow-ups to client-changes, and purchase orders to client-changes and purchase-orders. An answer to one of our queries will go to client-changes, whatever its kind, once it is linked as a reply to that query. The email that starts an enquiry is never queued. Both queues appear on the Mail Debug activity, an email’s own included. Nothing reads them yet, so such mail waits. See Limitations.
• Inbox: mail that follows a quotation is linked, as it is processed, to the enquiry and the quotation version it answers, by the first of these that matches: the quote number the customer cites in their own words, a reply to a quotation FlowOS sent, a quote number only in the subject, a reply to an email already linked, the same conversation, the customer’s reference, or, for a revision request or purchase order, the same client’s lines. A quote number without a revision means the quotation’s newest version issued or sent before the mail. Linked mail joins that enquiry’s card and follows its office and owner, unless it was reassigned by hand or the enquiry has no office, and an enquiry email that answers a quotation is typed as a revision request. Mail that matches several quotations or enquiries waits in Needs Review as ambiguous_quotation or ambiguous_enquiry, and a revision request or purchase order that matches none as quotation_not_found; an enquiry email with several matches is read as an enquiry, and mail Flowtech sends to someone outside Flowtech is never sent to Needs Review or moved to another office. A lead portal’s domain, such as TradeIndia’s, never identifies a client. See R97, R98 and Limitations.
• Inbox: the mail summary and the reading now include FlowOS quote numbers (FQ-…, with the revision) and earlier Q and T numbers, also when the client attaches a document that cites them. An attached document also gives the client’s RFQ or reference number, never a project or job number; a reference read only from an attached document links later mail, but does not group a new enquiry or fill the quotation’s customer reference. Our own quotation, proforma invoice, sales order, order acknowledgement, tax invoice, tag schedule, technical datasheet and packing list are never read for numbers. See Inbox.
• Choosing a product: a vortex flowmeter on a liquid is checked for cavitation at its size, from the velocity at its maximum flow, the liquid’s vapour pressure at its hottest temperature and the line’s lowest pressure, or against 1 bar g where the vapour pressure is not known. One that would cavitate is sized up while a larger size still reads the flow, and is ruled out, with the figures, when none does; a check resting on assumed conditions only warns. See R100 and R29 in Business rules.
• Choosing a product: DM, deionized and distilled water never take an electromagnetic flowmeter, whatever conductivity the enquiry states: they are non-electrolytic. A line naming one is a deviation offering the vortex flowmeter, then the turbine flowmeter. Such a line is no longer asked to confirm its conductivity, as it was under R97 since 2026-10-18. The library’s plain Water no longer answers to “DM water” or “demineralised water”, which now match only Demineralized Water. See R99, R88 and R97 in Business rules.
• Choosing a product: the clamp-on and insertion ultrasonic flowmeters, like the portable one, are offered only on a line that names them. They are temporary, externally mounted meters, not a stand-in for a permanent inline meter. See R27 in Business rules.
• Requirement gathering: a value an enquiry states once for a block of lines in its own words, such as a cable entry or a wire length above a schedule, is now written into every line it applies to as the lines are gathered, where the line states nothing of its own, and saved as stated with the passage it was read from. It fills only the one field whose label is the customer’s, case, punctuation and spacing aside; a label naming no field or several stays beneath the lines, and a conditional requirement fills nothing. Such a value no longer reaches some lines and not others from one gathering to the next. See R70 in Business rules and Line items.
• Line review and quotations: a fluid property from the library that would rule a line’s product out, but only warns because the enquiry states a figure FlowOS cannot read, is now asked of the customer. A DM water line on an electromagnetic flowmeter whose enquiry states “Conductivity >10 µS/cm” keeps the flowmeter, lists the conductivity under Ask the customer in line review, proposes it in Raise query even once the line is confirmed, and is flagged on its quotation line until the line holds a conductivity FlowOS reads. See R97 in Business rules.

2026-10-19

• Line review: a gas or steam flow saved converted on an assumed pressure, temperature or density, such as one taken at the 20 °C assumed for a line that states no temperature, now reads as assumed in the product suggestion, which cautions on a product it alone would rule out rather than ruling it out. On a line whose fluid’s phase is not known, a flow saved in Nm³/h stays as written, naming the phase as what it lacks, rather than being taken to an actual m³/h. A flow that cannot be converted again when the line’s pressure or temperature is saved keeps only its stated figures, and changing the fluid returns a flow taken to Nm³/h at a gas’s operating point to its stated figures. See Line items and Limitations.
• Unit converter: choosing a library fluid sets its phase as the library classes it, so Steam Reforming Gas converts as a gas and Gas condensate as a liquid, with its library density. See First sign-in.
• Unit converter: a Unit converter button in the top bar, on any page, shows a figure typed once, such as 1700 LPH, in every common unit of its quantity, and choosing a row copies it. Rows show five significant figures and copy the plain figure, 1666.7, with no separator or unit. A row that needs the phase, the fluid, the pressure, temperature or density, each in any unit, says so with an Add conditions link, which opens them (they open by themselves when the typed unit needs them, such as 100 kg/h); the converter keeps the last five conversions to load back. A unit can be picked from a list, found by plain spellings such as deg for °C, here and on the line review’s Unit boxes. See First sign-in.
• Line review: a range or number typed in a unit other than the one it saves in shows the figure it will be saved as, = 1.7 m³/h, under its input, with what it rests on when hovered, and Open converter, which shows it in every unit with the line’s conditions; Convert works its figures out with the line’s fluid and conditions, as saving does. A value that could not be converted for want of an input says which, such as the line’s operating pressure, rather than “Cannot convert m³/h to m³/h”. See Line items.
• Line review: a line confirms itself when Check these values leaves nothing open, no longer held back by a value Check leaves out (a figure a field already holds, a fluid name on a line with a fluid, or a conflict whose sides read the same). A gas or steam fluid the library does not hold is asked only for the pressure and temperature the line lacks, in the review and in the query to the customer. See R71 and R72 in Business rules.
• Line review: a line confirms itself when Check these values leaves nothing open, no longer held back by a value Check leaves out (a figure a field already holds, a fluid name on a line with a fluid, or a conflict whose sides read the same). A gas or steam fluid the library does not hold is asked only for the pressure and temperature the line lacks, in the review and in the query to the customer; one a requirement stated for several lines gives, or a temperature given as “Amb”, is not asked. See R71 and R72 in Business rules.
• Line review: Source opens the comparison view with the line alone, against the documents its values were read from, in place of a card in the review; where a document cannot be previewed, or the line cites none, that side shows the customer’s row. The comparison view’s headings and parameters read in sentence case, it marks values as the line’s review does, and an empty part of a range reads —. See Line items.
• Line review: Check these values leaves out a process value whose figures a field already holds in the same unit, unless it states the condition it was measured at, a fluid name on a line with a fluid, and sources that differ only in case or a trailing -ed or -d, such as “Flanged / Flange”; sources that disagree over the same values are one item, and their values read in the datasheet’s figures and units rather than as stored data. What it leaves out is listed under Also stated for this line. A figure whose unit the line’s row states in its own Unit, Engg. Unit or UOM cell is no longer flagged. See R81, R82 and Line items.
• Line review: a steam line whose cells state Vapour reads Steam in the header, and a fluid the library does not hold is asked its pressure and temperature on a gas or steam line, its concentration on a liquid one. Where the line states a liquid and the library fluid is a gas, or the other way round, the header cautions so. A line size holding no figure reads Not stated in the header, and its question for the customer no longer quotes it. See R81 and Line items.
• Line review: a temperature given only as “Amb”, with nothing assumed over it, is converted under Check these values, not asked of the customer. See R81.
• Line review: the Custom option’s code reads CU wherever it is named, and a value quoted as Custom reads Stated, as Custom (CU) on its datasheet row. The datasheet’s summary says how many stated values have an assumed range, then how many values print on the quote as assumed. Why this product writes units as the header does. See Line items.
• Line review: the confirmation note shows at the top of the screen, clear of the next line’s footer; the header’s band no longer repeats a value as its range, and a property whose ends are equal reads as one figure. On a phone the header’s band scrolls with the review, and the title wraps to two lines. A long option is cut short beside its item’s sentence. See Line items.
• Line review: every figure the review shows, in the header’s band, the datasheet, the change note and Convert, has at most four significant figures, so a pressure converted to 1.96133 bar reads 1.961 bar, and a range whose figures are all equal reads as one figure. A unit whose bracket the enquiry lost, kg/cm2(g, reads kg/cm²(g). See Line items.
• Line review: the datasheet opens on the heading holding the process values, with documents and calculation headings last; a calculation heading that holds nothing reads Worked out when the order is engineered. It names the groups its dots stand for, its summary’s parts add up to the fields it lists, and it counts the values the quote marks as assumed as the confirmed card lists them. A yes/no row reads Required or Not required, and one nothing fills Not required, Not asked. A value the fluid library gave reads From fluid, one the line’s other values gave Worked out. See Line items.
• Line review: an open datasheet row’s control is named by the row’s label and carries no origin chip or tint, a range’s boxes are labelled Min, Normal, Max and Unit, and where the value was read from reads “The enquiry says “50 NB” (attachment).” The note under a menu value reads “The enquiry says “PTFE”.” where it read “Customer wrote: PTFE”. See Line items.
• Line review: the fluid’s fold sums up a library fluid’s phase, specific gravity and corrosion, reads no pipe line number as the application, and opens without a second title; a guess is taken with Use and its name, an outline button, where it read Confirm. A corrosion warning on a guessed fluid is worded on that condition. The datasheet, the fluid and the other passages fold in one row pattern. See Line items.
• Line review: while a change waits on the family question, the line reads as saved; the question says why the former family no longer fits, as a sentence, which family fits and how many values switching sets from its defaults, and both its buttons are outline. Answered, the line reads as switched or kept, and the keyboard moves to the product strip. The change note is green, folds the values that follow the product’s defaults into one line with Show, and shows a spinner while the suggestions update. See Line items.
• Line review: Convert reads what follows @ or “at” as the condition a value was measured at, so “0.014 @ 3.5 Kg/cm2g” is a viscosity of 0.014 cP, Measured at 3.5 kg/cm²(g), not a range of 0.014 to 3.5; words with no unit take the field’s. A temperature’s “Amb” is placed as 40 °C, assumed, and the result names each figure of a range. See Line items.
• Line review: a value quoted as Custom is said once on its field. See R81.
• Business rules: the fluid’s state or nature with nowhere to go no longer stops a line confirming itself once its product suggestion is read, since the header shows it; a mixed state still does. See R71 and R72.
• Line review: the four groups each carry their colour, as a rule down the card’s left edge and a dot before its name, and the product strip and the folds below the groups are flat, the folds one list, so the open items stand apart. An item’s row lays out by the width of the review: its controls go under its sentence where the review is narrower, rather than squeezing it. See Line items.
• Line review: a guessed fluid is now a choice under Choose, with Use and the library fluid it was guessed as, which sets it as the line’s fluid, or Change…, which opens the fluid. It is no longer under Ask the customer or sent by Raise query while the line awaits review, and it still keeps the line from confirming itself; a line confirmed with the guess unused asks it of the customer. Ask the customer words each fluid item as the question asked, such as “Which fluid is “Caustic Lye”? We read it as Caustic Soda (50%).” See R81 and Line items.
• Line review: a field has one open item. Where it would sit in two groups, it stays in the first of Differs from the enquiry, Ask the customer, Choose and Check these values, with the other’s sentence after its own, and a question for the customer whose field holds no figure, such as a remark read into a line size, opens empty. See R81.
• Line review: Check these values no longer lists the fluid’s state or nature the enquiry gives with no field to hold them, which the header’s band shows. Another value with nowhere to go reads once, under the customer’s heading, with units and bracketed text as written, such as “Operating flow (m3/hr) max.” beside “Stated as “6”, and no catalogue field holds it.”, and keeping one keeps no other. A value whose passage lacks only a unit the line’s own column heading states, such as CONDUCTIVITY (µS/cm), is no longer flagged. See R81, R82 and Line items.
• Line review: a stated value no option matches says what the product does with it: “Not an option on this product; the quote carries it as written.” with Keep as written for Custom, its nearest option, or the option offered instead. A shared requirement’s wording is quoted. The items’ controls no longer carry origin marks, and Custom shows the customer’s wording as the menu’s value. See Line items.
• Line review: where a general name on the line fits several families, the product strip says so, such as ““Bypass rotameter” fits 2 families; the first is shown.”, and Choose reads “Pick between …” with a menu that picks the family. The strip shows the item code alone, the model number under Why this product, and a family level with the pick reads “Fits as well as the pick; listed after it by catalogue order.” Cautions on the product read as sentences, such as “The enquiry states CS ASTM A105, which this product does not offer.”, and “Customer wrote” no longer shows a percentage. See Line items and Glossary.
• Line review: the header now reads the line’s process under its title: the fluid, with the wording it was read from, the state and nature the enquiry gives it, then flow, line size, pressure and temperature, in the datasheet’s own figures, each with one word for where it came from and its range or wording beneath. The fluid’s density, viscosity and conductivity follow, with a caution where a stated density or viscosity is more than 15% from the library’s figure for a liquid. Choosing the fluid opens the fluid, and choosing a value opens its datasheet row. See Line items.
• Line review: the header’s title is the line’s service or location as the customer wrote it, put in sentence case where it is written in capitals, or the category where the line gives none; it no longer names a product family, which can be ruled out on the line. The tag falls back to the line’s tag number, and one row beneath gives the category, the quantity, which reads “1, assumed” where the enquiry states none, and the project. The line number, that row and the process band share one edge. Opening a line puts focus on its title. See Line items.
• Line review: Source opens at the top of the review, above the product strip, rather than in the header, so the footer stays on screen however long the customer’s row. The row is spaced like the datasheet. Compare with source replaces Open attachment: it opens the comparison view with this line alone, against only the documents it cites, and choosing a value there opens its datasheet row. A file missing from storage reads Preview unavailable in the comparison view, not an error page. See Line items.
• Line review: Confirm confirms the line with one click, and a note says which of its questions stay in Raise query. Only a line with unsaved changes asks first, listing them, with Save and confirm. The confirmation’s own review, and its Keep as stated, are gone; confirming still records each value the check marks as checked by the confirmer (R75). See Line items.
• Line review: the footer keeps every button on screen on a narrow screen, its status on a line of its own. Cancel reads Close, or Discard changes where changes are unsaved. Exclude can be taken back with Keep line, or Escape in the reason. While the line’s product loads, its open items and datasheet are placeholders and saving and confirming wait, the footer reading Loading the product…; where it fails to load they stay held, with Retry. See Line items.
• Line review: a line confirmed with no person is marked Confirmed automatically, as its card is headed, and the card says why without a percentage. See Glossary.
• Business rules: R75 now reads that a person confirms a line from its review, with no separate confirmation step.
• Line review and quotations: a menu value the line states or a person picks that the line’s product does not list at all, on a header with Custom, is now quoted as that product’s Custom option, worded as the value: the order code takes Custom’s code, such as CU, and the line needs a rate typed on the quotation. The line keeps the value as stated, with Quoted as Custom (CU): Flange-End under its Not offered by note, and its item under Check these values, on that field with Show in datasheet, says it is quoted as Custom. It still counts against the product’s fit, and takes its own code once the product lists it. A value the header lists that a mapping, another value, the size or a hard limit rules out is not quoted as Custom, and neither is a size the product does not list. See R78 and Line items.
• Line review: a line laid out as its product’s datasheet no longer shows Stated, not on this product’s datasheet or the link to the category’s other fields. The values the product has no row for stay on the line, and show on their rows if the product changes. A line with no product datasheet keeps Show all. See Line items.
• Line review: Show in datasheet is offered only for a field the datasheet draws as a row. A caution on the product has Why this product, and a stated value with nowhere to go has only Keep.
• Line review: Source shows the customer’s row as a table of their headings and values, the document it was read from (or From the email), and the quoted passages folded under Passages read. See Line items.
• Line review: a value the enquiry gave in words that hold figures, such as “approx 1700 LPH”, has Convert under Check these values. It opens a form that reads the figures and unit out of the words, shows them in the catalogue’s unit for the line, and with Use these figures sets them as an unsaved change. On a line awaiting review, such a value is not asked of the customer, under Ask the customer or in Raise query; a confirmed line still asks for it. See Line items.
• Line review: a changed value is read again before it is saved: the product, item code and filled values are suggested again with the unsaved values, and a note under the product strip says what the change did, Not saved yet until Save changes, with the values it moved tinted in the datasheet. Save changes waits while the line is suggested again, the footer reading Updating suggestions…; if that fails, saving goes ahead. A value a person set is kept as set, and the note says so. See Line items.
• Line review: a change that would move a line to another product family asks first, with Switch to the new family and Keep the former one, and Save changes is held, reading Answer the product question first, until it is answered. Keeping the family saves it as the reviewer’s pick. See Line items.
• Line review: each of the other options under Why this product has Use this instead, which picks that family for the line; the pick is saved with Save changes, before the values, and returns a confirmed line to review. The product strip then reads “Chosen in line review”. On a deviation the pick alone makes, the family the customer asked for is listed under Customer asked, not as ruled out, and what would have kept the picked family out, such as a type it is not, is listed among its cautions. A line with a reviewer’s pick no longer confirms itself (R71). See Line items.
• Line review: a line with a reviewer’s pick has Use the suggestion on its product strip, which clears the pick: the line shows what it suggests with no pick, the note under the strip reads Product pick cleared, and Save changes clears the pick before saving the values. See Line items and R96.
• Line review: a reviewer can pick the product family of a line. The pick is kept beside the family the enquiry asked for, ranks first, and is checked and sized like any other, with the limits it breaks kept as cautions. A pick outside the families asked for is a deviation, with the reason “Chosen in line review”, and saving it returns a confirmed line to review. The item code still follows the line’s size. See Line items and R96.
• Line review: choosing the family the customer asked for, under Customer asked, is saved as the reviewer’s pick: the line reads “Chosen in line review” and does not confirm itself. A fluid chosen on the fluid card is saved at once and can move the line to another family without the question. See Limitations.
• Quotations: a line whose family a reviewer picked prints the limits that family was chosen past among the line’s notes.
• Line review: a material the line’s product suggests that the fluid attacks, with nothing lining it, is now listed under Check these values. See Line items.
• Line review: a line whose product suggests a material the fluid attacks, with nothing lining it, no longer confirms itself when its product suggestion is read; it waits for a person (R71). See Line items.
• Line review: a value a person saves in a unit other than the catalogue’s is converted into the catalogue’s unit when saved, and the product suggestion reads the converted figure. A unit that cannot be converted is saved as written and not used. See Line items.
• Line review: a flow a person saves now converts on the line’s fluid, pressure and temperature. A gas flow in m³/h is saved in Nm³/h, taken at the line’s operating pressure and temperature as an ideal gas against an assumed 1.01325 bar atmosphere, with the library’s normal density for a gas matched with certainty; a mass flow converts with the line’s density, the library’s density for a liquid, or a gas’s normal density; and a steam flow in m³/h is saved in kg/h with steam’s density from the steam tables. An absolute pressure saved in review is read as gauge against the same atmosphere. A gas flow in m³/h on a line whose gas the library does not hold is saved in Nm³/h from the line’s pressure and temperature alone. A flow that still cannot be converted, such as a gas in m³/h on a line with no operating pressure, or a gas’s mass flow with no gas matched in the library, is saved as written with the input it lacks named. Saving the line’s operating pressure or temperature works the saved Nm³/h or kg/h figure out again from the figure as stated, so a flow saved before its pressure follows it. See Line items and Limitations.
• Line review: a line now opens on what needs a person. The product is one strip with Why this product folded beneath it, and the open items are listed in four groups: Differs from the enquiry, Check these values, Choose and Ask the customer. The datasheet is folded into read rows, each with one word for where its value came from, and the fluid is folded too. The To confirm card is gone. A value the enquiry states for no field that holds the line is listed under Check these values, the rest are folded under Also stated for this line, and what the enquiry left blank is one line under the groups. The datasheet, fluid, those values and the other passages are all folded. The header titles the line, with its tag, and the line’s wording is under Source. The footer reads N open, with N unsaved after it, and Raise query (n) opens the customer’s questions from it. A Keep is not saved: reopening the line lists the item again. See Line items.
• Line review: the list of lines now counts each line’s open items, in all four groups of the line review, as N open in place of N to confirm, N not found and N to check, and the bar above the list reads N open across M lines. Only lines awaiting review are counted, and those with something open still come first. Raise query asks nothing of an excluded line, and keeps the questions only the customer can answer for a confirmed one. See Line items.

2026-10-18

• Line review: a deviating line’s product card now shows what the customer asked for beside what is offered, why, with each reason’s deciding value and where it came from, and the line size and flow range. When a reason rests on a value the customer did not give, such as a conductivity taken from the fluid library, To confirm asks to check it under a new Product group, and the line no longer confirms itself (R81). See Line items.
• Quotations: the PDF prints a deviating line’s table under a Deviation heading: what the customer asked for beside what is offered, why, and the line size and flow range. A reason reads its bound in words, such as “at most 6 bar”. See Quotation builder.
• Quotations: a line that deviates from the family the customer asked for now keeps what was asked for, the family offered instead and why, frozen with the version when it is issued, in place of the note “The family the enquiry names was ruled out; an alternative is offered.” See Quotation builder.
• Product suggestion: a line that deviates from the family the customer asked for is now read with what was asked for, the family offered instead and why, each reason worded from the limit the line breaks and the line’s own figure, with where that figure came from. See Line items.
• Product suggestion: a family the customer asks for that is ruled out for any reason, not only for a flow it cannot read, is now followed first by its try-next families (R88). A “Bypass Rotameter” on a 25 NB line, below where either bypass family starts, is offered the metal tube rotameter instead of the acrylic body rotameter, shown as the listed substitute for the family asked for.
• Product suggestion: each bypass rotameter now lists the metal tube rotameter as the family to try next, kept on the Product Limitations screen beside the glass tube rotameter’s list (R88).
• Product suggestions: a flow meter whose line states its size only as the process connection size, such as “Line size: 200 NB” read onto that field, is now sized at that size when it reads the flow, as a stated main line size already was (R29). On a 22-meter electromagnetic flowmeter enquiry, 20 meters had been sized one or two sizes below the line; they now take the customer’s sizes, and two whose 100 NB line cannot carry 150 m³/h stay at 125 NB with a warning that the line looks mis-sized.
• Requirement gathering: a flow written as one figure, such as “50 LPH” or “10M3/HR”, is now read as the line’s operating flow, so the line can be sized. It used to stay as the customer’s wording, and the line asked for its flow rate.
• Product suggestions: a lining is no longer left off because only some of the wetted materials are graded for the fluid. When a material the fluid touches has no grade, such as carbon steel against sodium chlorite, the lining keeps its default and says which material was not graded, where it used to read “unlined: its wetted metal is graded A or B”. See R89 in Business rules.
• Product suggestions: a meter sized from its flow table now takes the line’s own size when that size reads the flow, or the closest size with an item code, where it used to take the smallest size that reads the flow and warn about reducers. A 50 LPH line stated as 25NB gets a 25NB metal tube rotameter, not a 15NB one. When the line’s size cannot read the flow, the smallest size that can is used, as before. See R29 in Business rules.
• Requirement gathering: a project the customer’s sheet spells several ways, such as “NTPC MEJA-2101”, “NTPC MEJA” and “NTPC Meja”, is now one project under its fullest heading, so an enquiry covering three projects shows three, not eight. See Line items.
• Requirement gathering: a fluid written with water, such as “CL02 & Water”, is now matched to the library’s solution of it, and “CL02” written with a zero reads as ClO₂. A gas such as chlorine dioxide named on a line that does not say gas is now read as its solution, as a guess to confirm, where it used to be read as the gas, which graded carbon steel acceptable and asked for a gas’s pressure and temperature. See Line items.
• Product suggestions: a fluid guessed without a strength, such as “HCL”, now grades the wetted materials and the lining on what every strength of it in the library agrees on, where it used to leave them unchecked: carbon steel and SS 316 are ruled out for hydrochloric acid, and a PTFE lining is taken. Its other properties still wait for a person to confirm the fluid. See R64 in Business rules.
• Requirement gathering: on a long schedule read in parts, a column one part left out, such as the line size, is now written into the field the other parts put it in, from the line’s own row and as written, where it used to be listed as having no matching field.
• Requirement gathering: a remark the reading joined to another cell, such as “Flow Tech; Flow Meter is under engineering.” in Branding, is cut back to the cell the field quotes, and the remark is listed with the row’s other unplaced values. An “Offered/Suitable Flow” written beside the required flow in the same unit, such as 16 M3/HR beside 6 M3/HR, is now read as the flow range’s maximum, where it used to be listed as having no matching field.
• Requirement gathering: a level indicator line that calls its item only a “Level Gauge”, such as “Level Gauge (Bulk Storage Tank)”, now narrows the choice to the reflex and transparent level gauges, where it named no family and the suggestion picked a magnetic level indicator. A type the line, its document or its enquiry names still comes first, so “LEVEL GAUGE” with a Type of “Magnetic type” stays a magnetic level indicator. Of the 22 dev lines that say “level gauge”, only the 10 that named nothing change. See Line items.
• Requirement gathering: a temperature, pressure or flow given as figures in one column whose heading orders them, such as “Temp (Min / Nor / Max / Design) °C” over “40 / 60 / 80 / 100”, is now read in that order, so its maximum is no longer lost, and a design figure there fills the line’s design temperature or pressure unless the line already holds one. See Line items.
• Line review: a valve or isolation valve material the enquiry states now decides a bypass rotameter’s ball valve material. A stated “SS316” isolation valve takes SS 316 – CF8M, marked mapped, where the line used to keep the SS 304 default and list the valve under “Stated, not on this product’s datasheet”. See R91 in Business rules.
• Quotations: a quotation that was never issued can be deleted. Delete quotation shows on an original draft, asks first, naming the number, and deletes the quotation with its draft. The number is not given to another quotation, so the series skips it, also when a PDF of the draft was downloaded. A quotation with an issued version cannot be deleted; the draft of its revision is still discarded. See Quotation builder and R85 in Business rules.
• Requirement gathering: a tag offered as two alternatives, each on its own datasheet naming a different family, such as a vortex and an electromagnetic flow meter, now stays two lines instead of being merged into one with the other’s values listed as conflicts. A line naming no family whose tag is on lines of two families is marked “Duplicate tag”. See R95 in Business rules.
• Product suggestions: six sizing figures that broke their own table’s rule are corrected. Five vortex steam cells now follow the size’s volume range times the steam density: DN32 at 18 bar has a maximum of 1632 kg/h, where 1614 was printed, and the minimums of DN32 at 7 bar, DN50 at 2 and 18 bar and DN80 at 12 bar are 66.006, 28.225, 226.6 and 367.6 kg/h. The standard metal tube rotameter’s 15NB minimum is 0.0025 m³/h, the 2.5 LPH its row gives, where 0.003 was printed. A flow close to one of these limits may now fit or miss that size differently. See Product limitations.
• Product suggestions: on a plastic line, a bare main line size that is a standard plastic pipe outside diameter is now read as that pipe’s nominal bore. A bare 225 on an HDPE line is sized at 200 NB and the line says so, instead of looking for a 225 NB instrument. Sizes with a unit, sizes a person entered and numbers that are also nominal bores are read as written. See R94 in Business rules.

2026-10-17

• Requirement gathering: a line’s quantity is no longer taken from its number of set points or contacts; an unstated quantity is 1, defaulted, and shown for review. See R73 in Business rules.
• Requirement gathering: an accessory listed as its own row beside the instruments it serves, such as an interconnecting cable in a scope-of-supply table, no longer becomes a line; it is kept as a shared requirement on those lines. See R72 in Business rules.
• Requirement gathering: a line whose fluid column says only “Liquid” or “Gas” now takes the fluid its service or location names, as a guess for a person to confirm, and a fluid column headed “Meida” is read. See Line items and R67 in Business rules.
• Requirement gathering: an instrument listed in both an item list and a datasheet is now one line, with any value the two disagree on, a fluid or spares count included, listed for checking. Two rows of one document with the same tag, lines whose tags overlap without being equal, and tags written in shorthand such as “LT-101/102/103” that share a tag with another line are marked “Duplicate tag”. A spares row carrying an instrument’s tag adds to that instrument’s spares with a note naming the row, unless the instrument states spares itself, when both are marked. A line holding an entry where its sources conflict no longer confirms itself when its product suggestion is read. See R71 and R95 in Business rules.
• Inbox: an enquiry’s reading now names the projects its lines are listed under, highlighted, with each project’s line count, so an enquiry covering several projects says so at a glance. See Inbox.
• Level switches: the number of set points now decides between side mounted (one), displacer (two) and top mounted (three or more). A line stating more than one set point no longer gets the side mounted switch. See R23, R27 and R28 in Business rules.
• Requirement lines: a line whose item or type starts with a product Flowtech does not make, such as a glass pot assembly with a level switch, is now excluded automatically with its reason and gets no product suggestion; a person can reopen it. The inbox board reads “Regret” when every line of an enquiry is outside range, and “N not in range” when only some are. See R92 in Business rules.
• Line review: a material with a finish, such as “MS + Epoxy” or “CS with epoxy paint”, now keeps its base metal, where it read as Custom; a tail that is not a finish, such as “MS + Rubber”, is read as no material. A list of materials written with their standards and grades, such as “CS A105 / SS304”, or ending “or equivalent”, is read as alternatives. Wording that refuses its material anywhere (“CS (not allowed)”, “CS is not acceptable”), or lists materials with anything else between them, is read as no material, and “PTFE lined” or “PTFE coated SS” no longer takes a PTFE option on a menu other than the lining. See R76 in Business rules.
• Product suggestion: blank wetted-part and connection menus now grade the options labelled MS or MS+Powder as carbon steel against the fluid (R79), since “MS”, “M.S.” and the other carbon steel shorthand are read as the material. See R76 in Business rules.
• Line review: a menu the customer words as several materials, such as “SS316 / SS316L”, now takes the product’s default when it is one of them, else the material the fluid suits best, else the first named, marked mapped with what the customer wrote, instead of Custom. A value worded as a minimum, such as “SS316 min.” or “weatherproof to min IP65”, takes an option that meets it, the default first once the fluid’s grades have ruled out any option they fail (R79). Wording that rules a material out (“not CS”), ties materials to parts (“body SS316, trim SS304”) or has a “min” that bounds something else (“min. thickness 3 mm”) is no longer read as a choice or a minimum; MS, WCB, A105, A106, A53, A36, CF8M and the S316 and S304 typos are read as the materials they mean; “SS316 lined with PTFE” gives SS 316 on a body menu and PTFE on the lining menu; and a stated option the product replaces with the same material it offers is listed in To confirm. A material an enquiry states once for all its lines is now decided by each line’s product as well, as a value on the line already was. See R76 in Business rules.
• Line review: a value the enquiry states under another product’s name for the same datasheet row, such as an operating pressure read as “Op. Press” for an orifice plate whose datasheet says “Operating Pressure”, now shows on the product’s own row and decides its menus. It no longer sits under “Stated, not on this product’s datasheet” beside a blank row. A stated end-connection material now decides a bypass metal tube rotameter’s main connection material, instead of the carbon-steel default, and a metal tube rotameter’s process connection. A line no product fits is laid out by the product the enquiry names instead of every field of its category. See R91 in Business rules.
• Line review: a text, number or range row the enquiry leaves blank now shows the picked product’s datasheet default, marked Default, such as a bypass metal tube rotameter’s isolation valve size. A default that says the value comes later, such as “After receipt of PO”, is shown as a note under the row. A heading’s filled count rises with them. See R90 in Business rules.
• Product suggestions: the material of the pipe an instrument is fitted to, its line MOC, is now read from the enquiry and shown on the line, and a plastic line steers the end connection to a plastic one. Where the enquiry leaves the end connection blank and the line is plastic, a rotameter whose connection is carbon steel by default is offered PP instead, unless the fluid’s grades or a stated header rule it out; where nothing suits it keeps the connection it had and the line waits in To confirm. A line whose pipe is plastic or FRP is no longer confirmed as it is gathered; it is left awaiting review so this rule decides it. A stated end connection stands, with a caution. Metal and lined lines are unchanged, and which materials suit which line is configuration. BMRM’s PP end connection, wrongly marked not applicable on the deployed catalogue, is offered again. See R93 in Business rules.
• Line review: a line no longer confirms itself when its enquiry is opened while a stated process value sits outside its fields, such as “Process temperature max: 180 °C” the reading placed in no field. That value holds the line for a person, as it already did when the line was gathered, since the line would otherwise be checked on an assumed 40 °C. A value the enquiry left blank, such as NA, does not hold it. On dev-aws, 21 of the 34 lines that would have confirmed themselves on opening now wait. See R71 and R72 in Business rules.
• Product suggestion: a fluid named only by its steam grade, such as LPST, MPST or HP ST, is now read as steam stated by the enquiry, as “LP steam” is, where it was a guess from the wording. A family whose guide does not cover steam is therefore ruled out on such a line rather than only warned of, and the line’s temperature and pressure are no longer filled in as ambient, as they are for a liquid. On dev-aws, 6 lines in one enquiry read this way. See Product suggestion.
• Fluid library: seven fluids that enquiries name are added: sodium chlorite (31%), chlorine dioxide solution (written “Water + ClO2”), isopropyl acetate, di-isopropyl ether, nitric acid at 5%, steam, and crushed briquette, held as a solid. Every value comes from a named public source: a safety data sheet, PubChem, or a maker’s resistance chart or dielectric table. A value no source states is left empty. Steam says it is not flammable, not toxic and does not conduct, with a maker’s dielectric constant; its density and viscosity stay empty, so steam lines are still sized from their pressure and temperature. Lines read before this keep their fluid until the enquiry is read again. See Limitations.
• Fluid library: plant wordings now name the library fluid they mean, so a line written that way matches it rather than being guessed or left unmatched: LP N2 and low pressure nitrogen are nitrogen; H2 is hydrogen; filtered, filter, backwash, UF backwash, degassed, WBA treated, service, UF product and UF treated water are water; raw and filtered condensate are condensate; DWPE, dewatering polyelectrolyte, synthetic flocculant solution and coagulant aid are the polymer flocculant solution; and liquor ammonia, as written or misspelt liqour, is the 25% ammonia solution, still a guess on strength but no longer read as ammonia gas. CIP water and regeneration water stay for a person to confirm, since they can carry cleaning or regenerant chemicals.
• Line review: after a line’s fluid is confirmed, chosen or recorded by name, the fluid card offers Apply to N other lines for the enquiry’s other lines still to review that word the fluid the same way, under the same project, with no fluid a person chose and no different liquid or gas reading, from the line’s fluid-state cell or else its fluid. Each line is listed and ticked, any can be unticked, and a line that refuses the change is reported while the rest take it. See Line items.
• Requirement gathering: a fluid cell that names only a class of fluid, such as “Acid” or “Chemical”, now gives way to the line’s service or installation location when that names a library fluid with certainty and repeats the cell’s class word; a fluid a location names is a guess. A fluid worded with plant after a semicolon, such as “HCl 33%; Dosing pump”, is matched on the fluid before the semicolon. Of the 362 current lines on dev, 6 read differently: two “Liquid” lines whose location is an RO permeate line are guessed as reverse osmosis permeate, two 33% hydrochloric acid lines are matched where they were guessed, and two lines with no fluid read water. The other 20 “Liquid” lines name their stream only in a location such as a pump discharge or an inlet, which names no library fluid with certainty, and stay as they were. Saved lines take the new reading once the substance backfill has run. See Line items.

2026-10-16

• Product suggestions: a lining the enquiry leaves blank is chosen from the fluid’s corrosion grades. A metal tube rotameter is unlined when its metal suits the fluid and lined with PTFE when it doesn’t, and is sized on the matching flow table, so a corrosive service is quoted at the lined size. The bypass metal rotameter no longer takes a PTFE lining for every fluid the chart grades. See R89 in Business rules.

2026-10-15

• Product suggestion: steam lines are sized on the steam’s density, worked out from the operating pressure and temperature, instead of on the 2 bar column of the client’s steam reference. A line holding none of pressure, temperature or density now can’t be sized, and above 100 bar abs it can’t be sized either. The reference’s 14 printed columns are used as printed, scaled to the line’s density. The temperature filled from a steam pressure beyond the reference’s 2 to 20 bar now comes from steam properties. See R29 and R84 in Business rules.
• Product suggestion: a limit can be tied to one datasheet option, such as a PTFE lining. A line that states another option is not held to it, and a line that states none warns and loses those options from the menu; a family left with no option but Custom is ruled out. Where a family has a flow table per option, the line’s own option picks the table, else the one the datasheet settles on, else the others with a caution. See R23 and R29.
• Product suggestion: a named family that can’t read the flow at any of its sizes is followed first by its try-next families, in order, with the rules still applied. The glass tube rotameter’s list is the bypass glass, then the bypass metal tube rotameter, whose flow ranges are not held yet. See R88.
• Product limitations: the reflex level gauge serves steam and liquids, on the client’s word of 2026-10-15. A limit can be set to apply when a datasheet option is chosen. See Product limitations.
• Product limitations: the page is now family-first. Families are listed by category with their rule and table counts and gaps flagged; the picked family shows how it is sized, its rules as sentences with their condition, effect and source (edited in a side panel), its sizing tables, try-next list and notes. Two more tabs list every rule and every sizing table across families, with search, filters and export. The old family dialogs are gone. See Product limitations.
• Inbox: an enquiry whose mail is on more than one conversation says how many on its card, such as “2 conversations”. Opening it lists the enquiry’s mail from every conversation, grouped by conversation under a header of its subject and the date of its newest mail, and choosing any email opens it, keeping the inbox’s tab, search and filters. Until now a card opened one conversation and nothing said there were others. See Inbox.
• Inbox: the panel beside an open email now follows the email’s type. A purchase order, revision request, follow-up or any other email that is not an enquiry shows the enquiry it belongs to, with Open enquiry email, also on another of the enquiry’s conversations, and the step still to come for its type, such as the PO check; it no longer shows the enquiry’s lines, Raise query or the quotation button, even on an enquiry’s conversation. Such an email shows a mail summary above it with its type, the quotation numbers and customer references it cites and, in Needs Review, the reason recorded. The Other mail rail is grouped by email type, each group with its count and Show all; a conversation with mail of two types is listed under both. See Inbox.
• Inbox: an enquiry email from the same client about the same requirement now joins the client’s enquiry for it instead of opening a second card, even on another conversation, such as the client writing again on a fresh email or a colleague forwarding it separately. It joins when it comes from the same address under the same subject as an email on the enquiry received within 60 days of it, and that subject carries a reference or project number; or, with no time limit, when it names the customer reference the enquiry carries and comes from the same address or company mail domain, never a webmail one. It never joins on the client alone, and when two enquiries could take it, a new one is opened. See Inbox.
• Item selection: a family that follows the line size, such as a sight glass or an orifice plate, now quotes the next size up when the stated size has no item code: a 225 NB line is quoted on the 250 NB code, with a note saying 225 NB was asked. With no bigger size the line stays not orderable. See rule R29 in Business rules.
• Requirement gathering: in a category read ten items to a call, a schedule column the calls put in different fields is now moved into the field most calls chose. Replayed over the eight saved enquiries holding such a category, 20 lines in three enquiries moved, each checked by hand: on one flow meter enquiry, pipe material read as flange material on ten lines now sits with the other 16 as existing pipe material. A value is never taken out of a field because other calls left its column unplaced, so a pipe inside diameter read as a Reynolds number on ten lines of that enquiry stays as read. See Requirement gathering.
• Datasheet editor: the grip for dragging a row to a new place in the row list is now always shown, instead of appearing only while the pointer is over the row. On a touch screen, which has no hover, it never appeared, so rows could not be reordered there. It stays hidden while the list is filtered by a search. On a touch screen, rows and a menu’s options can be dragged by their grip with a finger, and both grips are larger there so a finger can hit them.
• All screens: on a touch-screen laptop used with a touchpad or mouse, hover highlights and the controls that appear on hover now show; the browser reported such a laptop as unable to hover, so they did not.

2026-10-14

• Requirement gathering: the second request for schedule rows the reading left without lines is now made up to three times when its answer comes back empty or unreadable; it used to give up after one, keeping the short reading. Checked against the real model on BHEL Koderma: from an 8-line first reading, the second request read all 31 tagged rotameters. See Requirement gathering.
• Product suggestion: the top mounted level switch is now offered only on a line that states its stem or total length or the height of a switching point, as Flowtech needs them to quote it (R27). On a line with neither it is listed as ruled out, “offered only when the line states a stem length or switching heights”; a line that names it keeps it as the pick and needs the stem length. On dev data no suggestion changes; on six switch lines the top mounted switch leaves the list: the glass-pot float switch and four magnetic float switch lines, which now suggest the side mounted switch alone, and one line suggesting the displacer switch. See Product suggestion.
• Requirement gathering: a rotameter line that asks for an “Inline Rotameter”, “Online Rotameter”, “inline type” or “ONLINETYPE” now narrows the choice to the in-line rotameters (glass tube, metal tube, acrylic and tiny glass tube), where it named no family. Of 11 such lines on dev, and 11 locally, 9 were suggested a by-pass rotameter, the opposite type. Saved lines take the new names once the selection data fix and the family backfill have run. See Line items.
• Product limitations: three level switch limits from Flowtech’s own pages: the top mounted level switch is for a liquid of specific gravity above 0.7 with a stem of at most 3 m, and the cable float switch for a specific gravity of at least 0.8, so a lighter liquid or a longer stem rules them out. The conductivity switch’s minimum conductivity is not added: no Flowtech or maker page states it. On dev data no switch line’s suggestion changes; on local data ten dosing-tank level switch lines, each stating a guide tube of 1.2 to 2.5 m and four switching heights, move from the conductivity switch to the top mounted one, which the new checks now judge. See Product limitations.
• Requirement gathering: a level switch line is now named by the words enquiries use for its type. “Float type” and “float operated” narrow the choice to the side mounted, top mounted and cable float switches; “float / magnetic” to the side and top mounted ones; “side mounted”, “side entry”, “horizontal mounting” and “pivoted” name the side mounted switch; and a heading such as “Switching Principle” is read as naming the type. Eleven “FLOAT TYPE” lines on dev were suggested a displacer or a conductivity switch: five now suggest the side mounted switch and six, which state a 900 or 1410 mm length, the top mounted one. A glass-pot level switch with “Float / magnetic switching” moves from the displacer switch to the side mounted one. On local data these 12 lines are the only ones newly named. See Line items.
• Line review: a material the enquiry names that the line’s product does not offer now takes the menu’s Custom option with the customer’s wording, such as Custom “Hastelloy C”, where the menu has Custom, instead of the product’s default, which could be another material. A material the product does offer takes that option whatever its standard or form, so “SS304” takes “SS 304 ASTM A182 - Flanges” where the default used to win, and wording naming no material the reading is less than 50% sure of, such as “MS + Epoxy”, takes Custom too. A line holding such a Custom still confirms itself; Custom carries no catalogue price. Other menus are unchanged (R76, R32). On local data, of the stated materials no option names, 267 value-and-family pairs move from the default to the same material and 1,060 to Custom, and the reading’s closest picks of the same material are kept. See Line items.
• Product suggestion: a type the customer names that covers several families, such as “bypass rotameter”, now makes a deviation when none of them fits the line (R26), where it listed the best families of the whole job. On BHEL Koderma’s 25 NB bypass rotameter lines, which both by-pass families rule out from 50 NB, the clamp-on ultrasonic meter was the suggestion; the line now shows the by-pass metal tube rotameter ruled out and a glass tube, metal tube or acrylic rotameter as the alternative. On the 280 dev lines 24 suggestions change and no pick is left outside its line’s category (15 were); on the 327 local lines, 31 and 21. Four level gauge lines asking for a magnetic level indicator, which no family fits, now show it ruled out with its reasons instead of “no family fits”. See Business rules.
• Product suggestion: a family the customer asks for in the enquiry, in the line’s own document or in its subject or body, is now a Deviation when the process rules it out, as a family named on the line already was (R26). It used to be set aside without one: the line was suggested the best of the rest, with no chip saying the customer had asked for something else. On a consultant’s enquiry for vortex and magnetic flowmeters, seven lines of the magnetic sheet state a conductivity of 1 to 1.14 µS/cm, below the electromagnetic flowmeter’s 5 µS/cm; those seven lines now read Deviation, with the electromagnetic flowmeter named as ruled out, where they read Suggested; the product suggested in its place is unchanged (on dev data an orifice plate on two lines, a vortex flowmeter on four, an oval gear meter on one). A name FlowOS only inferred still makes no deviation. On dev data no other line of the 280 changes, and on local data none of the 327. See Business rules.
• Requirement review: a flow meter or rotameter line is now filled with the flow a quotation prints (R87): a minimum or maximum flow the enquiry does not state, at 0.7 and 1.3 times the normal flow, goes into the line’s flow range, and a blank design flow field takes 1.3 times the maximum. Each is marked inferred where it rests on stated figures and assumed where it rests on an assumed maximum; none chooses a size, and steam or a gas is assumed no flow. On local data 39 of 122 rotameter lines and 8 of 82 flow meter lines gain an assumed flow range, and no product suggestion changes on any of the 280 lines. No datasheet has a design flow field yet, so no line shows one; with that field, 79 flow meter lines and 63 rotameter lines would. See Line items.
• Product suggestion: on a flow meter or rotameter line, Why this family now has a flow row where nothing on the card judges the flow. Where the line states a flow and the family holds no flow range (no flow limit, and no flow table or flow span to size it by), the flow is shown as the customer wrote it, such as 0–33 M3/HR, with no flow range held for this family yet, neither passed nor failed. Where the line states no flow at all, a warning row reads not stated · not checked. A family sized from its flow table is unchanged: its flow is judged under Why this item code. On local data 105 suggestions gain the stated-flow row (53 by-pass metal tube rotameters, 36 orifice plates, 13 by-pass glass tube rotameters, 2 tiny glass tube rotameters and 1 clamp-on ultrasonic flowmeter) and 3 vortex flowmeter suggestions gain the warning. See Product suggestion.
• Product suggestion: a gas line is now sized on the acrylic, glass tube and metal tube rotameters at the density the line states, taken as at the line’s conditions, and only with none stated at its matched fluid’s library density; a gas whose fluid is only guessed, or not in the library, used to read “the flow cannot be read in the table’s terms”. A density written in kg/m³ under 20 on a line whose gas or steam phase is guessed from the fluid’s name alone, such as LP-N2, now reads as a density rather than a specific gravity, so 1.25 kg/m³ is no longer taken as 1,247.5 kg/m³ (R24). On local data the 18 LP-N2 rotameter lines are now sized, as assumed: the acrylic body rotameter they suggest at 1/4 in BSP, the glass tube rotameter at PG-3 and the metal tube rotameter at 15NB. The orifice plate takes the clamp-on ultrasonic meter’s place among their alternatives, and two nitrogen flow meter lines that state their density gain a 40NB metal tube size. No suggestion changes. See Product suggestion.
• Line review: a line whose product has no datasheet of its own now shows the rows every datasheet of its category carries, under a notice saying why, where it showed every field of the category. A rotameter line suggested the tiny glass tube rotameter, which has no datasheet yet, showed 70 rotameter fields, the by-pass rotameters’ orifice plate calculation among them; it now shows the 9 rows every rotameter datasheet carries, with Add datasheet, which opens a new decodification master for that item group. The same holds for a product of another category and for a line no product fits. The product, its alternatives and the line’s row in the list are named as the Item Master lists the item code, with its code and model number and a link to the Item Master, and as Item groups lists the family, with a link there. On a confirmed line the To confirm card is headed Confirmed by the person or Confirmed automatically, in place of a separate note above it. The review header no longer counts values by origin or by mark, which each heading of the datasheet already does. See Line items.
• Line review: the product now has a card of its own above To confirm, headed by its Item Master name, and its alternatives are listed as Other options, best first, each with whether it fits, its cautions and why it ranks below the pick. To confirm holds only what is left to settle, as numbered rows grouped under Needed to size, Fluid, Choose, Correct and Stated, no field for it, each with one line saying why it is asked (“Enquiry says HART Protocol. Not offered on this product.”) and its control at the right. A process value the enquiry left blank, such as ******, is listed once as left blank and no longer counted (R81): a flow meter line with two such values went from 8 left to 6. See Line items.
• Mail debug: the action on the selected email now reads Process again, and is offered on every email, not only enquiries. It processes the email afresh: classified again instead of from its saved classification, read and linked again, and, for an enquiry, gathered to replace its current requirements, review work included, with no confirmation asked. Permission to edit the enquiry is still needed once its requirements hold review work. An email no longer classified as an enquiry keeps its enquiry link and requirements. It replaces Gather requirements and Reprocess enquiry. See Requirement gathering.
• Product suggestion: sixteen families now carry a provisional ideal use, each read from Flowtech’s or another maker’s product page and quoted: the electromagnetic flowmeter for slurries, the metal tube rotameter for opaque liquids, the tubular level indicator below 5 kg/cm², the side and top mounted magnetic level indicators for toxic liquids and for corrosive acids and solvents, the reflex gauge for steam up to 20 bar, the transparent gauge for steam above it, the double window sight glass for steam, the vortex and IBR vortex flowmeters for steam, the oval gear meter for oils, the glass tube rotameter for clear fluids, the orifice plate and flange assembly for clean fluids, the clamp-on ultrasonic meter for clean liquids, and the insertion ultrasonic meter for lines above 1000 NB. Flowtech confirms or corrects them on the Limitations screen. On local data no line’s suggestion changes; six low-pressure water lines match the tubular indicator’s ideal use, which moves it ahead of the side mounted indicator among the alternatives on two of them, and on two steam lines the IBR vortex meter moves ahead of the insertion ultrasonic meter. See Product limitations.
• Product suggestion: a figure within 0.0005 of a limit now counts as at the limit (R23). A limit converted from another unit is held to three decimals, so a stated 5 kg/cm² (4.903325 bar) used to breach a 5 kg/cm² maximum held as 4.903 bar and rule the double window sight glass out; it now meets that maximum, and is still not below 5 kg/cm². On local data no line changes: none of the 3,923 numeric checks on 280 lines sits that close to a limit. See Business rules.
• Quotation: every line now prints its operating, minimum and maximum, and design temperature and pressure, and on a flow meter or rotameter its flow the same way, each marked Stated, Calculated or Assumed, or printed as Not stated (R87). Until now a quotation printed only what the line stated, put assumed figures in the notes and left out what was worked out from a stated figure, so on local data 204 flow lines had no design flow, 43 lost a calculated range and level transmitters printed no range or design figures at all. A lone flow figure is read as the normal flow, a minimum flow is 0.7 × normal, and the design flow is 1.3 × the maximum and does not choose a size. A rotameter’s scale prints as stated under its own label. See Quotation builder.
• Requirement gathering: a category with more than ten requested items is now read ten items to a call, and items a call left out are asked for once more. On one real enquiry of 47 rotameter lines the reading model planned all 47, wrote 8 and stopped, or answered nothing, and every try sent the enquiry to Needs Review; read ten at a time, all 47 lines are gathered. Gathered again over the nine saved enquiries holding a category of more than ten lines, every line of every category is read and none fails. See Requirement gathering.
• Requirement gathering: fewer enquiries reach Needs Review after a passing failure. A model answer that cannot be read is tried again, up to three times, where it failed the enquiry at once; a job cut off by the worker restarting starts again up to three times, where a second restart failed it; and an enquiry gathered again from Mail Debug is no longer sent back to Needs Review for its earlier failure while that job runs. Structuring and extraction are now sent to Amazon Bedrock alone, the one provider that accepts them, instead of reaching OpenAI and Azure first and being refused.

2026-10-13

• Quotation PDF: FROM now names the sales office, the sales representatives, the quotation number, revision and dates, instead of repeating the company in the letterhead; BILL TO lists every contact; pages after the first carry the quotation number and revision; each line shows its net rate. See Quotation builder.

• Quotation documents: besides the quotation, a version can be downloaded as a tag schedule (one row per line by tag number, with the totals and the amount in words, then the line pages and terms) or as a datasheet (one page per line, no prices or terms).

• Customer identification: when an enquiry’s signature text names no company, the logo in the signature is read for one. The client’s colleagues copied on a forwarded enquiry are kept. Each enquiry’s company is matched to the Party Master by GSTIN or name, with the branch chosen by PIN, city or state; the inbox card shows the match, or the likely companies. See Inbox.

• Quotation: the header holds a list of contacts in place of one attention, email and phone; existing quotations keep theirs as the first contact. A new quotation starts from the matched party and lists the customer’s people from the enquiry’s emails. With no company found, the customer name starts empty and must be typed before issuing, instead of the person’s name. See Quotation builder.

• Product suggestion: a line’s phase now comes first from a state or phase cell on the line itself, such as FLUID STATE: LIQUID, ahead of the fluid’s wording and the fluid library. A line that states its operating temperature and pressure is read as steam or vapour where its fluid would boil there: water against the catalogue’s steam tables, nine other liquids against their vapour-pressure curves. A stated gas or vapour on a steam line stays steam. On local data 75 lines take their phase from their own cell: 31 suggestions lose a warning that rested on an assumed phase, a liquor ammonia line matched to ammonia gas is now sized as the liquid it states, and a line stated as gas is sized as gas. See Product suggestion.

• Product suggestion: a family can now state its ideal use, a new kind on the Limitations screen beside hard limits, not-suitable entries, key limitations and installation notes. Among families that fit, one whose ideal use the line matches ranks after orderability and fewer warnings and ahead of the rest of the order (R28); a line outside a family’s ideal use is never a breach and never a warning. The product notice says what the suggestion is ideal for and whether the line matches it, and names ideal use when it put the suggestion ahead. No family states an ideal use yet; Flowtech’s entries are to be added on the Limitations screen. See Product suggestion.

• Product suggestion: each instrument type now names the inputs a line must state before its product reads as confirmed. A level switch no longer waits on a level span, and a level switch or level indicator needs its connection size. An atmospheric pressure assumed for a pressure transmitter no longer counts as its pressure. On local data 37 level switch lines stop asking for a span, 9 of them now ask for a connection size, and 5 read as complete. See Product suggestion.

• Product suggestion: a design or maximum pressure or temperature the line holds is now checked against each family’s limits. One the customer states rules a family out where it breaches a limit; one filled in by the design rule only warns. A line that states only a design value now counts as stating that pressure or temperature. On local data this clears a missing temperature on 11 level indicator lines and rules more families out on 30 flow meter lines. See Product suggestion.

• Requirement review: a blank design pressure or temperature is now 1.3 times the maximum, never less than 1.7 bar or 25 °C above it, where it was 1.5 times the operating value (R68). A line that states only an operating value takes the maximum R65 assumes, 30% above it. A maximum alone now gives a design value. A stated minimum below atmospheric marks the design pressure full vacuum. A design value the customer states still stands.

• Product suggestion: a flow line that states a normal and a maximum flow with no minimum now takes 0.7 × the normal flow as its minimum, where it took 0.6 × the maximum (R29). The design flow, 1.3 times the maximum, is Flowtech’s margin and does not choose the size.

• Product suggestion: a gas line whose flow is stated in m³/h is now sized. The flow is taken at the line’s own operating pressure and temperature and brought to Nm³/h, and the product notice says so with the figures. Until now such a line got no size and no item code, with the reason that the flow was not in Nm³/h. The line must state an operating pressure; a temperature it does not state is assumed and the size is marked as resting on assumed conditions. The value on the line stays as the customer wrote it. See Product suggestion.

• Line review: a line’s datasheet is now laid out as its product’s own decodification datasheet. The headings and the rows under them follow that datasheet’s order and use its labels, and blank rows show in place. Until now a line showed its category’s merged list, which for a flow meter is 114 fields under six headings ordered by how many products share a field, where an electromagnetic flowmeter’s own datasheet has 38 rows under three. A value the enquiry states that the product has no row for is listed under Stated, not on this product’s datasheet, and the fields of the category’s other products are behind Show other at the end of the line. A line with no product keeps the category’s headings. See Line items.

• Product suggestion: a line’s product notice now says why it is this family and this item code, without opening anything. It quotes the wording that named the family and where it was found, lists each of the line’s values that was checked against the family’s limits with the limit beside it, and marks a value taken from the fluid library or assumed. It names what could not be checked, what put the family ahead of the next one, and what the size and item code rest on. A family asked for and ruled out is named with what ruled it out. Until now the notice gave one sentence for the kind of answer, and the rest sat under Details or was not shown. See Product suggestion.

• Requirement gathering: enquiries waiting to be gathered are now caught up behind newly read mail, so a new enquiry is not held up behind them. The catch-up also looks only among mail that gathering covers; before, mail to other mailboxes could fill its list and keep newer waiting enquiries from being reached. See Requirement gathering.

• Requirement gathering: the second request for a schedule left without lines is more careful. A rate limit on it now makes the reading wait and run again instead of saving the schedule half read. An answer that reads the schedule but drops lines from another document is not taken. A line whose tag is written without its punctuation, or that lists several rows’ tags, now counts as reading those rows, so the second request is not made for rows that were read. See Requirement gathering.

• Inbox: the reassign form cannot be closed while it saves, so a failed save is always shown. The requirement panel’s bar says how many lines were confirmed automatically, where before only a hover showed it. An item group’s model number reports a failed read with Retry instead of loading without end.

• Requirement gathering: an enquiry that sends a magnetic flowmeter sheet and a vortex flowmeter sheet now names each sheet’s lines with that sheet’s family. On one real enquiry the 19 lines of the magnetic sheet that name no family themselves were named vortex flowmeters, and the product suggestion picked a vortex meter for them. A short type word such as “magnetic” in a document’s file name now names a family of the line’s own category, as it already did under a Type heading, and a specification the reading filed with one sheet but took from another is no longer read as the first sheet’s. Read again over 27 saved enquiries, only those 19 lines change. See Line items.

• Unit conversion: a flow the customer’s sheet gives in kg/cm², a pressure unit typed for kg/hr, is now converted as kg/h, with a note beside the value saying how it was read; the customer’s unit stays as stated. On one real enquiry six steam lines gave their flows this way and none was converted. A unit with a gauge or absolute mark, such as kg/cm2g, is left as stated. See Requirement gathering.

• Unit conversion: a fluid named only by its steam grade, such as LPST, MPST or HP ST, is now read as steam when its flow is converted, so the flow is kept in kg/h. Product selection already read these names as steam.

• Unit conversion: two ways of writing a unit no longer convert to a wrong figure. gr/cc is read as grams per cubic centimetre; it was read as grains, giving 56 kg/m³ for 0.865. deg K is read as kelvin. A gr in any other unit is left for review.

• Unit conversion: about 140 more ways of writing a unit now convert to the catalogue unit:

  • plurals and unit words: kgs/hr, Lts/Hr, Litres/Hour, M3/HRS, mms, cms, mm long, mm dia;
  • pressure: bar gauge, bar absolute, bar-g, mm of WC, mmAq, inch WC, ft WC;
  • temperature: degree celsius, Deg Cel, Deg Cent, degcelcius, ºC, Kelvin, and a bare deg or degrees, read as °C with a note;
  • flow: M3/MIN, KLPH, LPD, cu.ft/min, Te/hr, PPH, GM/HR, Nm3/hrs, Ncum/hr, Std. m3/hr, Scm/hr, MSCFD;
  • density and viscosity: kgs/m3, ton/m3, pcf, Sp.Gravity, Centipoise, kg/m.s, Ns/m2, Centistokes;
  • marks: ℃, mPa·s, a typographic inch mark ” and a foot mark '.

  What still stays in the customer’s unit is listed under Limitations.

• Requirement gathering: a second reading of thin lines that answers for only some of them is no longer thrown away. On one real enquiry the reading model returned 6 of the 10 lines it was asked for again, the whole answer was refused, and all 10 lines were saved with two fields each. The lines such an answer does return are now kept, and the ones it left out are asked for one more time. See Requirement gathering.

• Requirement gathering: a schedule the reading model left without lines is now asked for once more. On one real enquiry the model returned no line for any of the 21 rows of a second sheet, and the enquiry was gathered with 24 lines out of 45 and nothing to say so. Where most tagged rows of a table became no line, the model is asked a second time with those rows named; where rows still are not lines, the enquiry is saved with what was read and carries an unresolved note, Rows not read as lines, that names them. See Requirement gathering.

• Requirement gathering: an operating pressure, an operating temperature and an operating flow range that the customer’s row gives in separate Min., Nor. and Max. columns are now read from those cells, each into its own place, with the heading’s unit. Until now the reading model filled them, and on a wide schedule it could leave the maximum out or write the normal figure as the minimum. A value is no longer listed as stated with no field to hold it only because the columns beside it state the same value, as three cells saying “Amb” do, or because another column of the row holds the same figure. See Line items.

• Requirement gathering: a line that names no product family now takes the one its own document names: in the file name, or in what the document states once for its lines, such as the Type row of a specification sheet. Until now only the email’s subject and body were read, and an enquiry naming two families there, such as “vortex flowmeter and magnetic flowmeter”, left every line unnamed. Each line now takes its own sheet’s family, and a document naming several narrows the line to those. The family is recorded as named in the enquiry and is checked against the line as before. Lines already gathered change when their enquiry is gathered again. See Line items.

• Requirement gathering: a line’s fluid is now the substance the instrument handles, as the customer wrote it. A Service or Application cell that names no tank, pump or line is read as the fluid whether or not the library holds it; until now it was kept as the application and the line showed no fluid. What a dosing or storage name holds is read as the fluid for a person to confirm, so “NAOH dosing tank” gives NAOH and a drawing titled for a storage tank gives what the tank stores. A line code in the fluid column, such as “PR”, gives way to a substance the row names elsewhere; where the row names none it stays as written and the fluid is asked for. A tank, pump or line name is kept as where the instrument is installed. The Service row of the line’s datasheet, and so of its quotation, now shows that same substance as written: no longer “RAW WATER; LIQUID” with the phase joined on, and no longer a tank name where the row gives no substance. What was joined on is kept with the line as stated with no field to hold it. Lines already gathered change when their enquiry is gathered again. See Line items.

• Requirement gathering: a line read from a row of a table now holds every cell of that row, under the column’s full heading with its unit and any Min., Nor. and Max. sub-heading. Until now the reading could leave cells out of a wide schedule, a drawing title or a row’s operating conditions among them, and could write a tag differently from the sheet. A value no field takes is listed under the line as not placed, as before. A table whose headings cannot be matched to its rows, a datasheet with one property per row, and a scan or picture read from the file stay as read.

• Requirement gathering: a line of an attached document read from its text now counts as read only when every word and figure of it is passed on, in a line’s fields, a shared requirement or the additional information. A line the reading cited but kept only in part, in a PDF table, a datasheet or a paragraph, is now kept whole as an unresolved passage, as a line nothing cited always was. Until now a cited line was taken as read however little of it was kept.

• Connected systems: calls to the model behind the contact reader, the picture reader and requirement gathering can now be recorded in Langfuse, a tracing service, once it is set up for an environment. The text a model was sent and the text it answered are recorded only for mail delivered solely to a mailbox requirement gathering covers, which is the test mailbox today. For all other mail only the reader, the model, the timing, the token counts and the email’s id are recorded. No attachment file is ever sent. Connected systems has what goes out.

• Requirement comparison: choosing a value in the comparison matrix now opens that line’s review at the value’s field, outlined and ready to type in, with its heading or the Show all link opened for it. Until now the line opened at its top and the field had to be found.

• Requirement comparison: on a smaller screen the comparison matrix and Compare with Source now fill the window, and the matrix columns narrow to the room they have, so more lines stay in view beside the source document. A line’s column heading is two rows, with its review state as a coloured dot where the column is narrow. The counts of lines sit in the title bar. The Back to Extraction and Close buttons are gone; the cross and the Esc key close the screen.

• Inbox: the action panel beside an open email now leads with the enquiry’s lines. Shared requirements, unresolved requirements and additional information are each folded to one row beneath the lines and open when chosen. The bar above the lines is one line: the lines confirmed, what is left to confirm and the revision. Reply to Email, Raise query and the quotation button stay at the foot of the panel while the lines scroll, with the quotation button leading on an enquiry. The same foot names who the email is assigned to; a person who may reassign chooses that line to pick an office and an owner. The purchase-order and sales-order placeholders show only on an email that belongs to no enquiry.

• Requirement gathering: an enquiry’s requirements are now gathered by themselves. Once an email is read as an enquiry and a catalogue category is confirmed, gathering is queued with no action on Mail Debug, while requirement gathering is switched on and covers the email’s mailboxes. An email read while it is paused is gathered once it resumes.

• Requirement gathering: an enquiry that has requirements keeps them when a later email of the same conversation is read as an enquiry. That email shows in the conversation with nothing gathered from it. Until now it stayed hidden until someone gathered it, and gathering it replaced the requirements.

• Mail debug: the action on an enquiry gathered before reads Reprocess enquiry. It gathers from the selected email again and replaces the enquiry’s current requirements, with the same protection for review work as before.

• Requirement gathering: enquiries read before gathering started by itself, or while it was paused, are now gathered too. Resuming queues them at once, and while gathering is on the worker looks for them every five minutes. Each used to need the action on Mail Debug. An email whose gathering failed stays in Needs Review and is not tried again by itself.

• Requirement gathering: up to three enquiries now have their requirements gathered at the same time. Each used to wait for the one before it to finish. Two jobs for the same enquiry still run one after the other, never together.

• Decodification Master: the Priced by… menu on an option now reads Fixed amount and By parameter, the words the Pricing Library already uses, in place of Per option and Per unit measured. How each is charged has not changed.

• Decodification: the Model number at datasheet defaults strip now follows the datasheet’s gates, inheritance and conditional rules, on the datasheet view, the item group view and in the editor. A header its parent switches off no longer adds a segment, so the strip shows the model number a released code is given. In the editor it updates a moment after an edit, and a note takes its place while a row in the draft is incomplete.

2026-10-12

• Guide: the Guide entry in the product now opens the handbook at its own address, where its pages display and link correctly. Opened inside the product, the pages lost their styling and their links led to the sign-in page.
• Handbook: four diagrams are redrawn to match the product. Processing layers puts reading the files before naming the stage, and shows the quotation and the flag on a quotation that needs revision as built. The pricing diagram says an option with no rate adds nothing and flags its line, and that a default option is in the base price. Worker jobs and Mail to processing show one job per email and the stored email’s real key, and draw only the child process per job and the autoscaling as not built.
• Handbook: rules that had drifted from the product are corrected. R7: a message the labelling service is unsure of is treated as an enquiry, while one it cannot be reached for is tried again and then goes to Needs Review. R25: a ruled-out named family leads the Ruled out list, with the best alternative as the suggestion. R59: an overwritten price is recorded in the audit log. R71 and R72: a line is confirmed from its product suggestion only when someone with inbox approval opens the enquiry’s lines, a value whose unit could not be converted holds a line, and so does an unplaced quantity, spare or total.
• Handbook: the email types are the seven the inbox shows (Enquiry, Revision request, Quotation, Purchase order, Sales order, Follow-up, Other) on Message labelling, Lifecycles, Capabilities and Automatic behaviour. Limitations lists the inbox and the catalogue masters as live screens, and no longer lists a size written in a product’s name, or milk of lime, as gaps. Needs Review and unassigned mail are described as shown to everyone who reads across all offices, a shared mailbox as belonging to no office, and a mailbox as paused or resumed, not removed.
• Handbook: Connected systems now says what requirement gathering sends to the outside models, and Automatic behaviour lists office routing and automatic confirmation. First sign-in says the handbook opens without signing in.
• Handbook: the catalogue pages now say that the Pricing Library has no control that removes a price, that an option is judged against its position’s process factors today, that an item code’s default selections decide what its price includes on a quotation, and that a group’s first published datasheet becomes its current one. Reference data describes the Substance Master, and the item code examples use the electromagnetic flowmeter’s own prefix.
• Requirement gathering: a size written as “mm NB”, “NB mm”, “mm DN” or “DN mm”, such as “300 mm NB”, is now read as a nominal size. A millimetre figure outside the nominal series is still refused.
• Inbox: the head office is placed in the Gujarat zone, beside Ahmedabad, so its Office Head shares the Gujarat enquiries routed by region.
• Documents: a scanned PDF attached to an enquiry is now transcribed to text by the picture reader, once the email is typed as an enquiry and while model calls are on, and marked as read from a scan. It is sent only when every mailbox the email was delivered to is one requirement gathering covers, which is the test mailbox until a zero-retention agreement is recorded; otherwise it is still listed as needing character recognition. Requirement gathering reads a transcribed scan like a PDF that has converted text. A transcription that stops before the end of the document, for a scan or a picture, is discarded and the document listed as not read (R50). R49 now says a picture or scan is asked once more only after a temporary fault of the picture reader; one that came back empty, was cut off or ran out of time is listed as not read at once.
• Requirement gathering: an item described in a paragraph, as on a tender page, is no longer repeated whole under its line as not placed. Only the parts no field holds in the customer’s words, and no unresolved requirement with no matching field quotes, are listed, with an ellipsis where a part was taken out; a part is taken out only as whole words and figures, so “SS 316” held in a field leaves “SS 316L” listed (R72).
• Inbox: a query to the customer can now be raised from an enquiry. Raise query, under the quotation button, lists what each line still to confirm needs from the customer: the fluid, flow rate, line size, measuring range, a gas line’s temperature and pressure, a steam line’s pressure and IBR approval. Untick what you will not ask, add your own questions, and Write email opens the reply with the query template filled in, lines asked the same questions under one heading. The compose dialog’s “Discrepancy / Clarifications” template is now Query to Customer. A reply to a colleague’s forward now greets the client contact the reading found, not the colleague, and a reply to an email of ours is addressed to that email’s recipients.
• Inbox replies: only a person whose role lets them send inbox replies now sees Reply to Email and may send. Of the seeded roles those are Sales Person, for their own enquiries, Office Head, Administrator and Developer. A reply goes from a mailbox the conversation arrived in: your own, or a shared one, which on an enquiry you may work on can belong to any office, so mail routed to your office is answered from the mailbox the customer wrote to. Without an enquiry the shared mailbox must be your office’s, and a colleague’s own mailbox is never used. On an enquiry’s conversation the customer’s answer comes back to the shared mailbox of the enquiry’s office (R55). To, Cc and Bcc take up to ten addresses each with none repeated, and the subject up to 255 characters. A reply Microsoft has accepted shows as sent at once, a reply whose result is uncertain is never removed from the conversation, and one stuck on Sending can be sent again after three minutes.
• Requirement gathering: a line’s fluid is now read from every place the enquiry states it. A fluid written once for a document, such as “Fluid: Water” on a datasheet covering several tags, reaches each of those lines. An upper and a lower fluid are read: the lower one is the line’s fluid when the upper one is a gas, and two liquids are both kept for a person to choose. A service, application or installation location is read as the fluid only when it names a library fluid, so a tank name such as “caustic dosing tank” is read and “sludge holding tank” is not. An installation location or position gives no fluid or phase by its wording alone, so “steam turbine hall” is not read as steam. Line review shows such a service as the application the enquiry gives in place of the fluid, where it used to say the wording was not in the fluid library. A value stated under a liquid heading that the reading could not place now holds its line for a person (R72).
• Quotations: a line’s options can now be chosen on the quotation. Options on a line lists them in code order, and on a draft each is a menu of what the product offers for the line. A choice is saved on the enquiry’s line, not on the quotation, so line review, the model number, the price and every quotation for the enquiry follow, and a confirmed line goes back to not confirmed in line review (R45). Custom wording stays in line review, the options of a product from another category than its line cannot be chosen here, and the product and item code still cannot be chosen from either place.
• Quotations: a draft now takes its payment split from the terms template’s price rules: the first rule whose delivery option is the quotation’s and whose price condition its basic value meets, which is the goods after discounts and before charges and GST. It follows as the value or the delivery option changes, and falls back to the template’s default where no rule matches or the totals are pending. The terms card says where the split comes from. A split typed on the quotation stays as typed and is marked Edited for this quotation, with Use the template’s rule to go back. Issuing freezes the split shown (R45). A revision keeps a typed split, and otherwise follows the template’s rules and default again.
• Quotations: the Issue dialog now shows the grand total it will freeze, and issuing is refused when the quotation changed after it was opened, whether someone else saved it or line review or the catalogue moved its grand total; the quotation reloads and nothing is issued (R45). Issuing is also refused while a change typed on the quotation is withheld (R36), and Issue is held back, with the reason beside the button, while an edit on the page is unsaved.
• Quotations: a withheld change now shows what it set, its quantity, rate, discount or skip, beside the reason, on a card that says what to do: enter it again on its line if it still stands, and dismiss what is left. A discount of zero is no longer kept or listed (R36).
• Quotations: Revise now asks first: the new draft becomes the latest version and the lists show it in place of the issued one.
• Quotations: the draft of a revision can now be discarded. Discard draft asks first: the draft’s edits are lost, the quotation goes back to the last issued version, and the lists show that version and its total again. An original draft cannot be discarded, since its number is already taken (R85).
• Quotations: a line’s quantity can now be set on the quotation, and clearing it goes back to the enquiry’s. It is carried into a revision, frozen on issue, and withheld like a rate when its line changes. A line quoted at a quantity the enquiry does not state is flagged in amber and counted in the banner until a quantity is set.
• Quotations: what the enquiry states once for several lines now reaches each of them on the quotation: it prints in the operating conditions and design specifications, picks the price band and prices per-unit options. A value held as text, an option or a yes/no answer now prints, a range with one bound prints as “min 5 m³/h” or “max 80 °C”, a figure keeps the unit it was stated in unless its conversion held, and a line’s tag and stated service print. A Custom option’s wording prints however the option came to be chosen. Vortex and turbine flowmeters, orifice plates and orifice flange assemblies now print their design specifications.
• Quotations: a line whose product comes from another category than the line, such as a rotameter line quoting an electromagnetic flowmeter, now has that product’s defaults filled in, and names both categories over only the options still open.
• Quotations: a price deduction now prints with a plain hyphen, “- ₹800.00”; the minus sign it used is not in the PDF’s font and stopped the PDF. An option priced by a rate table is now priced when its rates were saved against the size alone, as it was when they were saved against its own header; the catalogue’s price previews read such a table too. An option charged per unit measured whose figure the line holds in another unit than the rate is per, or with no unit, or whose datasheet names no unit for it, now adds nothing and is flagged with the unit named, where the figure was multiplied as it stood (R37). A line priced by a rate typed on the quotation no longer carries add-on figures.
• Quotations: the PDF now prints the buyer’s GSTIN and the place of supply under BILL TO, and each line’s item code and GST rate. Every page carries the quotation number at its foot, with the DRAFT mark on a draft, so a page a long line runs onto and the closing page are marked too. A tax rate prints as 18%, not 18.000%. An add-on with no price prints “Not defined” on a draft only. A character the PDF’s font does not hold prints as a placeholder mark and no longer stops the PDF, and a letterhead website saved with https:// no longer prints the prefix twice.
• Quotations: Quotes Needing Revision now lists a quotation when a revision request arrives on its enquiry’s conversation after it was issued. It looked only at the emails the reading links to the enquiry, which are enquiries, so a revision request sent as a reply was missed. A request sent as a new conversation is still not found.
• Quotations: a line’s quantity, rate or discount whose save fails now goes back to the saved value with a note to enter it again. A save refused because someone else changed the quotation reloads it and says the unsaved changes were not saved. Switching revision, or closing or reloading the page, asks first while a change is unsaved. Packing that is switched off no longer needs a percentage, and each box is checked as it is typed: payment parts as whole numbers from 0 to 100, validity from 1 to 365 days, discounts, charges and rates within range, and at most 30 clauses.
• Quotations: a quotation now moves with its enquiry when routing gives the enquiry an office, as it already did on reassignment. Generating one while no terms template is active is refused saying so, and a change to a line that is no longer on the enquiry is refused in plain words and reloads the quotation. The application a new quotation starts with is that of the first line it includes, where that line states one.
• Handbook: the quotation pages now match the product. R36 covers a rate, discount, quantity or skip typed on a quotation, and R38 says an unanswered option stops the issue while an unconfirmed line only warns and a draft PDF prints what is open as open. The place of supply is the state chosen on the quotation header, not the delivery address. Confirming or excluding a line in line review needs inbox approval, which the Office head role holds and the Sales person role does not. A line’s product and item code cannot be chosen yet. The application is typed on the header (R40). An issued quotation does not record the datasheet version it was priced against. The capability catalogue marks the quotation capabilities Live, and the line saying an enquiry with a quotation cannot be deleted is removed, since nothing deletes an enquiry.
• Quotations: typing again the quantity the reading defaulted now sets it on the quotation, which clears its amber flag; it was read as no change. A card saved after someone else changed the quotation is now refused and the quotation reloads, even where the page had refreshed in between; that save went through and undid the other person’s change. Rates saved against a second thing a header’s price depends on, such as a flange bore, are not read by the line’s size: the option adds nothing and the line is flagged, saying what the rates are listed by (R37).
• Quotations: options marked as affecting the price now price the line whether or not they are in the order code, such as packing or the protection grade. A deduction prints as “− ₹800.00”. A line is left unpriced when its chosen option is no longer on the datasheet, an option is charged by a quantity the line does not state, or deductions bring its price to zero or below (R37). The client’s flow range in the design specifications is read from the same flow field as the price band.
• Quotations: a line’s notes now list only its deviations and the values the platform assumed; the customer’s unplaced wording and sizing notes are no longer printed. Figures on a line print with at most two decimals, or three significant figures below 1 (“1.37 bar”).
• Quotations: Open enquiry beside the quotation number opens the enquiry in the inbox, on the conversation its board card opens; it shows only to someone who may open that enquiry’s mail.
• Quotations: only options marked as affecting the price change it; the default option is in the base price; another option adds or subtracts its rate (R37). An option marked as not affecting the price, or not reviewed yet, changes nothing. A price setting for a row the line’s datasheet does not have changes nothing. A line is now priced when another option has no rate or no charge method in the item master: that option adds nothing (+₹0) and is listed on the line in amber, saying what to fix, with a marker beside the rate and a banner above the lines counting such lines. A line not yet confirmed in line review is quoted too, flagged the same way. Neither stops the issue, and neither is printed. An item code with no price or no price band covering the flow, an unchosen option that affects the price and a Custom option still leave a line unpriced. A price band is now picked from the flow figures in the line’s operating conditions, converted to m³/h, Nm³/h or kg/h, and the printed operating conditions list every value the line states there under the datasheet’s own labels. A quotation cannot be issued while the company profile’s state is not on the list of states (R86), and an office already named “… Office” no longer prints “Office office” on the letterhead.
• Quotations: the place of supply on a quotation and the state on the company profile are chosen from the list of Indian states and union territories, and a quotation cannot be issued without a place of supply (R86). The letterhead prints the issuing office’s name, email and phone. The PDF leaves off charges at zero (R42), prints its totals from gross through the discounts to the grand total, and states the share on credit as a percentage. CGST and SGST are equal halves of each rate’s tax. A line excluded in line review cannot be included on the quotation. The quotation lists show a draft’s grand total, marked Draft, and its lines ready to issue, as of the last time the draft was opened or saved.
• Requirements: gathering now reads the client’s words quoted below a colleague’s reply to colleagues that says nothing of its own. Such an enquiry was already recognised and assigned from the quoted text, but its lines were gathered from the attachments alone: what the client wrote in the email was missing from the line, and an enquiry with no attachment went to Needs review with nothing to gather. A line gathered before this keeps what it holds until its enquiry is gathered again.
• Requirement gathering: a PDF that has converted text is now read from that text with the file beside it: every value comes from the text, and the file decides which column heading each value belongs to. Since 8 October such a PDF had been read from the file alone, which left values out and wrote ones the document does not hold, and the check could not catch it because it compared the reading with itself. These PDFs are checked against their converted text again. A scanned PDF and a picture are still read from the file. A line gathered from a PDF since 8 October keeps what it holds until its enquiry is gathered again.

2026-10-11

• Quotations: the Quotation card beside an enquiry now generates a quotation, numbered FQ-yy-yy-nnnnn per financial year (R85); an enquiry can have several. A draft is rebuilt from line review on every view and shows why each line cannot be issued, and lists overrides withheld because their line changed (R36, R45). Only the header, terms, charges, overall discount and each line’s rate, discount and exclusion change on the quotation. Issuing freezes a version; revising makes -R1, -R2. GST is now charged per line at its HSN rate, with CGST and SGST inside the company’s state and IGST elsewhere (R41, R86). The PDF is previewed and downloaded in the browser, with a DRAFT mark on a draft. Quotation lists: List of Quotations, Quotes Pending to be Sent, Quotes Needing Revision. The Terms Master carries standard clauses and a new Company profile page holds the letterhead. FlowOS does not send quotations yet, and there are no accessory lines.
• Requirement review: each line now opens with a To confirm list of only what stands between it and a quotation: an input the product needs, a steam line’s pressure and IBR type, a fluid to settle, a menu the product leaves open, a value that cannot be saved and a process value with nowhere to go, with the line’s product shown above them as a notice (R81). Headings fold to one line each, and the category’s other products’ fields sit behind one link at the end. A value whose passage reads the same as it is no longer marked red; the passage shows quietly beneath it (R82). Lines with something to confirm are listed first, with each project’s count. A liquid line with no stated temperature or pressure, or only wording with no figure for one (“As per process”), now counts the assumed 40 °C and 0 bar g as known (R16, R17); a gas line asks for both, and a steam line for its pressure and IBR type (R84). A menu the product offers one option for takes it (R83). A menu the customer named in words no option means now takes the reading model’s closest option when it is at least 50% sure and the product offers it, otherwise what the product decides, its default or a condition, with what the customer wrote beneath it, and To confirm lists it to check; Custom is chosen only by a person (R76). Requirement reading now reads a comma-packed ERP material description token by token (size, rating, an unlabelled C/C length on a level gauge, and anything left over kept as unplaced), tells the reading which product families a field belongs to, and understands lengths in CM. A line that states its size only in the item’s name, such as “Rotameters 80NB”, now has that size (R29). A fluid the line names that the library does not hold, such as a mixture, no longer leaves the product unverified once the line states its density or specific gravity (R28). Menus that copy a material from another, or are asked only for some of its options, now follow a menu filled with its only option (R83). A line whose product, a deviation included, has a size and whose To confirm has nothing missing now confirms itself, marked Auto-confirmed, unless a default replaced something the customer wrote or a person has worked on it (R71).
• Requirement review: every menu, yes/no field and accessory now says where its value came from: stated, mapped (with what the customer wrote and the percentage), Custom, decided by a condition (with the reason), a default, edited, or unresolved, with up to three options to pick in one click. A menu lists only its catalogue options, those the line’s product offers first, and “Customer wording” is no longer a choice on a menu or a yes/no field, which offers Required and Not required. Accessories are a list with quantities; a stated list also shows the product’s default components it does not name until a person removes them. A stated value the line’s product does not offer is marked, and a header the product switches off is listed as not needed, with the reason. Only the menus the product leaves open are listed as left open; one it has no row for is closed as not set by it. Library values take up to 30 other wordings, which a customer’s wording is matched against.
• Product suggestions: a header the fluid touches now reads the fluid’s grades through the material each option names, whatever form of the metal the option is, so a default graded A or B is kept rather than swapped for another form of the same metal. For a fluid that is mild overall, such as water, a default the chart grades D stays (R30); one graded C is still replaced. A header whose options name no material, such as a connection type, is left alone without a note (R79).
• Product suggestions: a line’s pick, when it is of the line’s category, now carries its datasheet options for the line — stated, mapped, Custom, decided by a condition (a mapping, a process value, the size, a copied material or the fluid’s corrosion grades), defaulted, or left for a person — and a stated value any family that fits does not offer counts as a warning in the order (R77–R79). What the customer stated now outranks a mapping from a header we filled, a Custom value is never refused by a mapping, and a hard limit broken only on an assumed value, or on a library value of a fluid no person has confirmed, warns rather than refusing what the customer asked for (R34, R62). The line’s review shows the pick’s options.
• Requirements: stated menu values, yes/no answers and accessories are now matched to catalogue options as they are read — by name, by another wording of the option, or by the reading model when it is more than 80% sure — instead of being kept as the customer’s wording. What the customer wrote is kept beside every value.
• Datasheets: rows that carried two default options now say what decides between them — the electromagnetic flowmeter’s flange standard by line size, the side-mounted magnetic level indicator’s float by its chamber, the reflex gauge’s cover plate and connection by its chamber, the float-and-board indicator’s parts by its float, and the bypass rotameter’s scale for PTFE-lined bodies.

2026-10-10

• Inbox replies: authorized operators can send acknowledgement or clarification replies from a conversation. Acknowledgements require a next review date. Replies use the conversation’s receiving mailbox and are recorded in FlowOS; sending requires Microsoft Graph to be enabled by an administrator. FlowOS shows when a reply is sending, checks Sent Items before marking it sent, and checks the existing message before retrying an uncertain timeout.
• Requirement review: each line in the list now shows its suggested product, the family with its item code, or why there is none, and its size, in place of the enquiry’s wording, with a chip: Suggested, Deviation or No product fits. The wording stays in the row’s hover text and in the line’s panel, which gains a Product section with the pick, what it still needs, the alternatives and the families ruled out with their reasons. A suggestion is not a confirmation.

2026-10-09

• Choosing a product: rules R23–R28 now describe how FlowOS chooses a family for a line. Among limitation entries, only a trusted hard limit or not-suitable entry breached by a value the customer stated, a reviewer saved or a matched fluid holds rules a family out; assumed values, an assumed phase, a guessed fluid, key limitations and single-source limits only warn. Every family the customer names is checked and kept on the list, even one from another job, and only a named family that is ruled out makes a deviation. On a line that names nothing, the line’s own category is listed and the list widens to the whole job, with a notice, only when nothing there fits. A line that states a C-C distance or insertion length leaves out a family with no such datasheet entry; a stated float size the datasheet does not offer only warns. A family named only in the enquiry’s subject or body, when those names agree, is judged like a named family but makes no deviation when ruled out. Families offered only when named are not listed otherwise. Price plays no part in the order (R28). Names are read from the line or the enquiry, not inferred. The ranking is computed for each line; it is not on screen yet.
• Choosing a product: families are now sized for the line: the smallest size that reads the whole flow, with its item code, a warning when the meter is smaller than the line, and a flow written “0 to 450 LPH” read as a scale from zero rather than a duty at zero. A family no size reaches is ruled out, and only warned of when the flow it is sized on rests on an assumed value or table basis, or a table could not be read. A flow with no minimum stated is sized from 0.6 × the maximum; a size that reads the stated flow but not that assumed minimum is still chosen, with a warning. A float the fluid grades C or D is sized on with a warning rather than skipped, and a gas or steam line against a liquid-only table is left unsized rather than ruled out. Some families still show “Sizing not available”. Families orderable from the line’s own data now rank first, with sizing headroom ahead of the margin (rules R28, R29).
• Choosing a product: a density written under 20 kg/m³ on a line that is not gas or steam is read as a specific gravity and only warns, and a library gas that may be liquid at the line’s conditions (liquefied, cryogenic, or commonly handled as a liquid) is only warned of, through phase, density and viscosity (R24).
• Limitations screen: editing a web-sourced limit’s title keeps its sources, and these are refused: clearing its document name, an edit that would join its sources to another limit’s, a title another limit already has, and a rename of a limit whose sources another limit shares.
• Requirement review: confirming a line now first shows the values you changed (as first read and now), the values the check still marks, each with Keep as stated or Edit, and the values assumed for the line. A kept value shows Checked by your name in place of its mark, and confirming the line checks whatever is still marked, so a confirmed line keeps no marks. Confirming then opens the next line still to confirm, and a confirmed line shows who confirmed it, when, and what it was confirmed with, with no Confirm button. See R75.
• Requirement gathering: a pressure a datasheet gives as one figure with both an absolute and a gauge unit, such as 1 Bar A Kg Cm2, is read in the gauge unit (1 kg/cm²), since pressures are worked in gauge, with a note beside the value; it was kept as unreadable wording. Kg Cm2 written without a slash now converts like kg/cm².
• Requirement review: a value marked Check this value now says the check found it but was not fully sure of it, rather than that it may belong to another line.
• Requirement review: the check is now told which line a value belongs to by the line’s own row, not by its position in the enquiry. On a sheet with one table per project, where each table numbers its rows afresh, this had marked correct values as conflicts. Gather an enquiry again to clear marks saved before this.
• Requirement review: every percentage is now support, how sure the check is a value was read correctly; a line shows its lowest. The “Conflicts with the enquiry” mark is now Not found in the enquiry, a lean of less than half the vote is Unsure, and a weakly supported value is Check this value. A value found implied with more than 80% support no longer stops a line confirming itself.
• Requirement datasheet: a figure with no unit in a density or specific gravity field is shown as a specific gravity (“1 sp. gr.”), not in kg/m³.
• Requirement review: a value the reading could not place holds its line for a person only when it describes the process (flow, pressure, temperature, density, viscosity, the medium or the duty). A make, a remark or a part number stays listed under the line and no longer stops it confirming itself.
• Requirement gathering: a line’s quantity now includes the spares its row states, shown as “Qty 5 incl. 1 spare”. A row whose stated total is not its quantity plus its spares keeps the total and waits for a person, with the difference listed under the line.
• Requirement review: each line keeps the project, site or package it is listed under. Where an enquiry lists lines for two or more projects, the panel groups them by project and numbers them within each.
• Corrosion warnings: a stated wetted material is now also checked when it is Hastelloy C, titanium, aluminium, tantalum, copper, PFA, neoprene or acrylic, and PTFE, PP, PVC, PVDF, SS 304 and SS 316 are graded for more fluids, from published resistance charts. A steel part named together with a PFA or neoprene lining, or with glass, now gets no warning about the steel, because the wording names two chart materials.
• Fluid library: 21 slurries, among them Coal Slurry, Cement Slurry, Kaolin Slurry and Sand Slurry, now show as conducting on the Substance Master and beside a requirement line’s fluid, as water-based slurries do; they had been marked non-conducting. Five liquids that did not say whether they conduct now do, from magnetic flowmeter makers’ conductivity tables: coffee extract and whole milk conduct; lard, dimethyl sulfate and molten paraffin wax do not.
• Catalogue: IBR Vortex Flowmeter, Ultrasonic flowmeter (insertion and portable types), Acrylic body rotameter, By-pass glass tube rotameter, By-pass metal tube rotameter, Tiny glass tube rotameter, Top mounted level switch, Cable float switch, Conductivity level switch, Differential pressure transmitter, Double window side glass and Full view side glass now carry operating limits taken from Flowtech’s and other makers’ published pages, each kept with the page and the exact line it came from. The limits are listed on the Limitations screen; quotation and selection do not apply them yet.
• Inbox: enquiries enter Active only after manually queued requirement gathering succeeds. Pending mail is hidden from all inbox users; terminal extraction/gathering failures are administrator-only in Needs Review. An enquiry whose requirements were gathered stays in Active while it is gathered again. Successfully processed unassigned mail is held for Administrators and Developers.
• Inbox: New is per person and contains ready enquiries with conversation mail they have not opened. Opening mail moves the card to To review or Ready to quote for that person alone.
• Sales Office Master: added State/UT coverage configuration by routing zone. The initial State mapping follows the approved Sales Office sheet; matched mail routes to the active Office Head in the covered offices who was assigned the least mail in the last 30 days. Mail in a person’s own mailbox stays with that person, and a reply follows its enquiry. A person who may not edit offices sees each zone’s coverage and cannot change it.
• Item groups: a family’s view, and its current master on the Decodification screen, can download the family’s price sheet as a PDF for a trader: every size side by side with its item code and base price, each price-driving header’s options with what they add at each size, the options only quoted on asking listed once, and a key to reading it. List prices, marked confidential for the named recipient. See Price sheet.

2026-10-08

• Catalogue: the electromagnetic flowmeter sizing table now includes the ten released sizes from 550 to 2200 NB that the sizing reference leaves out, worked out from its velocity basis of 0.3 to 5 m/s. Each carries a note that it is derived, shown in the flow-sizing export.

• Catalogue: in the datasheet’s price preview, entering a line’s operating pressure or line size limits the pressure-range options of the smart and miniature pressure transmitters, and the sensor-size options of the clamp-on ultrasonic flowmeter, to those that cover it. The pressure transmitters’ Custom option is always offered.

• Requirement datasheet: units are shown the way engineers write them: KG/CM2 as kg/cm², kg/m3 as kg/m³, M3/HR as m³/h, deg C as °C, and Kg/cm2 g as kg/cm²(g). This changes the display only. The unit field still holds the customer’s own text, and a unit the screen does not recognise is shown as written.

• Catalogue: process connection and jacketing sizes are now held in NB, not millimetres. A stated 25 NB or DN 25 now fills the field as 25, and 2" as 50 NB rather than 50.8 mm. Enquiries gathered before this keep millimetres until they are gathered again. See Nominal bore.

• Requirement review: a converted value’s information mark now lists what it was converted with: the stated density, or the library’s density or normal density with the fluid named, an assumed atmosphere, and assumed reference conditions or unit readings. A gas or steam flow converted to Nm³/h or kg/h on a field held in m³/h shows as converted, in that unit. Changing a line’s fluid returns a value converted with the previous fluid’s library density to the figures as stated.

• Unit conversion: a mass flow now converts to m³/h with the density the line states, else the one the enquiry states for every line, else the fluid library’s density for a liquid the line matched with certainty; a guessed fluid gives none. A gas flow is standardised to Nm³/h, with the library’s normal density for a gas matched with certainty, and a steam flow to kg/h. An absolute pressure converts to gauge with an assumed atmosphere of 1.01325 bar. Each converted value records the density, atmosphere or reference conditions it relied on, and where each came from.

• Unit conversion: a figure the customer wrote as an inch fraction, such as 1/2, 1-1/2 or 1½, is read as its decimal.

• Unit conversion: no model writes a conversion formula any more. The units service performs every conversion, with the line’s density where one is needed, and a value it cannot convert stays in the customer’s unit for review.

• Unit conversion: many more ways of writing a unit now convert to the catalogue unit:

  • pressure: KSC, ata, mWC, mm Hg, kg/sq.cm, psid;
  • temperature: ℃ and ° C;
  • volume flow: CMH, cum/hr, LPS, KL/hr, KLD, MLD, USGPM, IGPM, GPH, CFH, BPD;
  • mass flow: TPH, Kg/Hr;
  • density and viscosity: gm/cc, SG, °API, cps, mPa·s;
  • conductivity: micro S/cm.

  A size written in inches is read on the nominal-bore table, so 1-1/2" is 40 NB. A barrel is the 42-gallon oil barrel, and a ton is the metric tonne. Atmospheres (atm, ata) are recognised as absolute pressures.

• Unit conversion: a figure the customer wrote in words or under a combined heading, such as 3/ 4 under “NORM/MAX PR. KG/CM2”, is now read into its numbers and unit and converted to the catalogue unit. A model reads it; the reading is kept only when every figure and the unit appear in the customer’s own text, and otherwise the wording stays as written.

• Unit conversion: worded figures are read up to 25 fields at a time, so on a large enquiry one slow reading no longer leaves every wording in the category unread. While the model provider is rate limiting, gathering waits and starts the email again instead of keeping the wording.

• Requirement review: compare lines in a parameter matrix and read cited attachment or email-body evidence beside it. The matrix marks conflicts, conversions, inferred and assumed values, and fields edited in review.

• Requirement gathering: the Branding field of a rotameter now tells the reading what it holds, which is whose nameplate the instrument carries. The make and the instrument type had been filed under it.

• Requirement gathering: a cell that only asks the vendor for the value, such as VTP (vendor to provide), VTS or “vendor to specify”, is no longer saved in a field. “MAKE: VTP” had been saved as a branding value.

• Requirement gathering: a PDF with text is read from its converted text again. Reading it from the file, introduced the day before, left values out on some documents. A scanned PDF and a picture are still read from the file.

• Requirement review: unit aliases that Pint identifies as the same unit are shown as standard, while real conversions show their converted values and formula. Unrecognized units have their own review mark, distinct from physically incompatible units; neither blocks saving. The Converted Values badge now sits at the end of the field marks.

• Requirement review: values derived through model-selected unit formulas and fields that remain incompatible now stay in human review; rejected pressure-reference and nominal-size conversions are not sent to formula resolution.

• Unit conversion: common uppercase notation such as M, KG/M3 and L/H is interpreted as metres, kilograms per cubic metre and litres per hour, rather than unrelated case-sensitive units.

2026-10-07

• Requirement gathering: nothing an enquiry states for a line is dropped any more (R72). A line that placed few of its row’s values is read once more, and any value still placed in no field is kept with the line under the customer’s own label, marked not placed.
• Requirement gathering: a PDF of up to 10 MB is now read from the file itself, so a table with headings on several rows, or one continued over a page, keeps its column labels. Its converted text is used when that fails. A PDF or picture read from its file is checked against what was read from it, since its converted text is not what the reading saw.
• Requirement gathering: one answer from the check that cannot be used no longer loses the whole reading. That value is left unchecked and its line is left for a person.
• Requirement review: a line holding a value the reading could not place is not confirmed automatically (R71).
• Requirement review: each line now lists, under its datasheet, what the enquiry states for that line and no catalogue field holds, as Also stated for this line. Requirements that belong to the whole enquiry stay under Enquiry context.
• Inbox: the Active tab is a board with New, To review and Ready to quote columns. New is personal to each user and means the user has unopened conversation mail; the other columns reflect requirement progress. Mail that is not an enquiry is listed in an Other mail rail beside them, with the email-type filter. A due date reads “Overdue” once it has passed, and is marked as soon from today to three days ahead. The list view remains on Needs Review.
• Inbox: mail now follows its assignment. A person sees the mail assigned to them even when it arrived in a shared mailbox or someone else’s, and mail assigned away leaves the first person’s list. An enquiry’s assignee and the head of its office can read every email of its conversation; a reply read this way is reassigned by whoever sees it by its mailbox or its assignment. An office head now sees the requirement lines of an enquiry that has no office yet, and can review them once it is assigned into an office.
• Unit conversion: rejected unit tokens remain flagged for review and are not passed to formula resolution.
• Unit conversion: the worker maps requirement values into formula variables; the units service evaluates the bounded numeric expression.
• Unit conversion: a units-service outage no longer blocks requirement gathering; the stated requirements are saved without derived standard values.
• Unit conversion: cubic-volume shorthand now respects prefixes, and inch nominal sizes map to NB/DN designations through a size table. Gauge and absolute pressure annotations are recognized; changing the pressure reference and converting normal-volume flow without reference conditions are refused. Assumed operating values use the converted range’s unit.
• Requirement review: values converted to the catalogue unit now show in that unit with their stated figures and conversion formula available beside the field label. Units whose converted value already matches the catalogue value are shown as standard; unsupported unit conversions are cautioned without blocking review.
• Requirement review: compatible converted operating values now drive the assumed pressure and temperature ranges and design margins in the same standard unit. Editing a converted value saves it in the catalogue unit; an incompatible value keeps its stated unit.
• Requirement review: a line is now confirmed as it is gathered, with no person, where the check supports every value it states with more than 80% confidence, its quantity is stated and its fluid is not a guess (R71). It shows as Auto-confirmed, the bar above the lines counts these apart, and editing a value returns the line to review. Such a line does not stop the enquiry being gathered again. Lines gathered earlier are confirmed the same way by a one-off backfill.
• Requirement review: a value marked as conflicting with the enquiry now shows the passage it was read from, whether that passage reads the same as the value, and how sure the check was. A line with conflicts says above its sections what a conflict covers. Until now the mark stood alone, with nothing to compare the value against.

2026-10-06

• Requirement review: what the enquiry states once for several lines is now filled into each of them (R70). A shared requirement that names a catalogue field, such as an output signal asked of every instrument, shows on every line it applies to, marked stated, where the line states nothing of its own. One kept in the customer’s own words, and a conditional one, still sit beneath the lines only.
• Requirement review: a line no longer counts its blank fields. Each heading of the datasheet now says how many of its fields are filled out of the fields it has, and the list of lines shows the same figures per heading. Each line in the list now also labels its quantity, shows its fluid coloured by how sure the match is, and runs its description to two lines. Menus, the options that make up the model number, are left out and counted apart as chosen with the product. See Line items.
• Requirement review: the bar above the lines now leads with the lines confirmed out of those to settle, and gives the fields filled across every line. The Unstated fields filter is withdrawn: with every category listing all its families’ fields, it matched every line.
• Requirement review: a blank design pressure or temperature is now filled at 1.5 times the operating value, never below the maximum, and marked assumed (R68). A category’s range field now holds the same minimum and maximum as its operating field: a stated one is copied across as inferred, and an assumed range is filled into both (R65). Both come only from figures the enquiry states, not from an assumed ambient value.
• Requirement review: what the enquiry states is never replaced by a filled value (R69). A density, specific gravity or viscosity the customer gave under one field now stops the fluid library filling that property into another field beside it.
• Business rules: R68 and R69 are new. R16 and R65 now cover a range copied between a line’s fields.
• Requirement review: a figure the customer stated without the catalogue’s unit, such as a specific gravity in a field held in kg/m³, is now shown on the datasheet as their wording. It used to show as not stated, though it was saved.
• Requirement review: a fluid the library does not hold can now be recorded on the line by name. The datasheet then asks once each for its density or specific gravity and its viscosity, where the enquiry gives none, and what the reviewer enters is saved as edited in review. A person who may create catalogue records can add the fluid to the library from the line, with the form opened from what the line holds (R67).
• Requirement review: values the enquiry does not state are now filled in on the datasheet when a line is opened, with no step to use them: the fluid library’s density, specific gravity and viscosity as inferred, and ambient conditions and the range around an operating value as assumed. Each says beneath what it rests on, and is saved only when the reviewer changes it, as edited in review. The separate list of assumed values is gone.
• Requirement review: every value on the datasheet is marked stated, inferred, assumed or edited, and each section counts its fields by origin. A line with conflicts, a guessed fluid or assumed values says so above its sections, and a fluid the library does not hold is marked in red.
• Requirement review: a field a person has saved in review is no longer filled with an assumed range or an ambient figure. The saved value stands (R17, R65).
• Business rules: R66 (a filled value is saved only when a person changes it) is new. R16 and R24 now name inferred values beside assumed ones, and the glossary treats inferred and assumed as two origins.
• Mail debug: the Pipeline Progression Tracker now shows the tokens and estimated cost of each stage’s model calls, and an estimated total for the email. Emails processed earlier show Cost not recorded.
• Inbox: the browser’s Back button now returns from an open conversation to the conversation list. It used to leave the inbox for the page visited before it.
• Mail debug: the selected email has an Open in inbox button, which opens its conversation in the Global Inbox with that email selected.
• Requirement gathering: a PDF the document reader could convert is now read from its converted text. A scanned PDF, which has no such text, and a picture are still read from the file itself.
• Connected systems: the contact reader, the picture reader and requirement gathering now use one model, OpenAI’s GPT-6 Luna, reached through the Vercel AI Gateway, in place of the DeepInfra models and Gemini. Signature blocks and enquiry pictures, and for the test mailbox an enquiry’s text and attachments, are sent to the gateway, which routes each call to OpenAI or Amazon Bedrock. No zero-retention agreement covers it yet.
• Requirement review: the enquiry’s passages that are not catalogue fields now sit below the datasheet, to read beside the line. Attaching a passage to a line is withdrawn.
• Requirement review: a value the scoring pass found to conflict with the enquiry is now marked in amber on the datasheet. Rose marks only a value that cannot be saved, such as a minimum above its maximum.
• Requirement review: a line’s fluid is matched in more of the ways customers write it: by an abbreviation the library gives in brackets, by a formula written with its strength, and whatever the word order or spacing. Steam is no longer read as water, a qualifier in brackets such as “Water (DM)” is no longer dropped, and a mixture of fluids is left for the reviewer rather than matched to one of its parts.
• Requirement gathering: an operating pressure or temperature written as plain figures, such as “1.5-6” under a column headed in bar, is now saved as numbers with its unit, so the assumed range around it can be offered (R65). Three figures are read only under a column headed minimum, normal, maximum. Wording with a qualifier, no unit or no figure is kept as written.
• Requirement review: an operating pressure or temperature the customer wrote only as “ATM” or “ambient” is now offered atmospheric pressure or 40 °C beside the line, to use or not, whatever else the line states. R17 says so.
• Requirement gathering: requirements gathered earlier can have their worded operating pressures and temperatures read into numbers by a one-off backfill, with no model call. It skips a line that has been confirmed, excluded or edited, and a field it rewrites loses its scoring verdict, which was given on the wording.
• Requirement review: wording the library does not hold is now guessed from the words it shares with a library name, from one misspelt word, or by the reading model choosing among a few similar library fluids or none. Where no library entry is near a stated strength, the guess is the nearest entry rather than the strongest. Every such match is a guess and is read from only once confirmed (R64).
• Fluid library: four plant wordings now name the fluid they mean: thermic fluid is heat transfer oil, DI water is deionized water, milk of lime is lime slurry, and polyelectrolyte is the polymer flocculant solution. “Liquid chlorine” is no longer read as certainly the library’s chlorine, which is held as a gas with a gas’s density; it is a guess for the reviewer to confirm (R64).

2026-10-05

• Substance Master: catalogue maintainers can view, search, and manage catalogued process fluids and gases, including physical constants, thermodynamic properties, Antoine vapor pressure parameters, wetted material chemical resistance ratings with inline rating entry, and alloy corrosion rate observations with test condition details in an interactive slide-out drawer.
• Requirement review: each line shows its fluid, matched to the fluid library from the customer’s own wording, with the library’s properties beside it. A match made on shared words, or at a strength the enquiry does not support, is a guess: nothing is read from it until the reviewer confirms it or picks another fluid from a search of the library.
• Requirement review: values the enquiry does not state are offered beside the line and saved only when the reviewer uses them: the library’s density, specific gravity and viscosity, ambient 40 °C and atmospheric pressure, and a range 30% either side of a lone operating pressure or temperature.
• Requirement review: a material the customer asked for on a part the fluid touches is flagged when the published chart grades it C or D for the line’s fluid, on requirements gathered from now on.
• Business rules: R64 (a guessed fluid drives nothing until confirmed) and R65 (the assumed range around an operating value) are new. R17 now says that any stated figure for a quantity, a design value included, stops ambient conditions being assumed for it.
• Requirement gathering: operators can queue source-linked extraction for one classified enquiry from mail debug. Classification and requirement-gathering model calls have separate pause controls and start paused, so queued requirement jobs wait until resumed. Results are stored with the enquiry and reviewed in the inbox; quotation handoff is not yet available.
• Requirement gathering: an enquiry is linked only when its saved reading confirms at least one catalogue category. Unconfirmed readings remain unlinked and cannot be queued for gathering.
• Requirement gathering: an enquiry takes the office and person its email is assigned to, or the intake mailbox’s office and owner until then, and its requirements move with it when the email is reassigned. A follow-up in the same thread joins the thread’s enquiry instead of starting a second one. An enquiry with no office is visible only to all-office users and its assignee.
• Requirement gathering: until a zero-retention agreement covers the gathering models, only an email delivered solely to the test mailbox can be gathered; any other is refused when queued and again before anything is sent.
• Requirement gathering: gathering again no longer discards review work silently. Once a line is confirmed or excluded, or a field is set by a person, it is refused until the operator chooses to discard that review, which needs permission to edit the enquiry.
• Requirement gathering: a job that fails stays on the debug page with its step and reason, and a failure that would repeat is not tried again. A confirmed category with no requested item, and an attachment with no readable content, are left out and named rather than failing the job. An evidence excerpt is at most 150 characters.
• Requirement review: users limited to their own or their team’s work can now open and edit the requirements of enquiries assigned to them or their team. Editing a field of a confirmed line returns the line to review. A value is shown in the unit the customer stated, a failed save says why beside the field, and an enquiry with nothing gathered shows as empty rather than as an error.
• Requirement gathering preview: a requirement stated for every item of a category is now matched to catalogue options, verified and saved once with the category, where it was previously left out of the saved result. Verification reads only original source lines, never the structuring step’s own reading of them.
• Requirement gathering preview: the preview extracts each category the enquiry holds requested items for, says where that differs from the categories detected, and keeps the categories that completed when another one fails. Passages the structuring step attached to no item now reach catalogue extraction in full.
• Requirement gathering preview: where masters of one category describe a field differently, the field’s heading and type no longer depend on the order the masters are read in, and a master’s accessory list is offered as a field.
• On the rail: Item Group Master, Item Master, Decodification Master, Pricing Library and Mail Debug are listed as live screens. The product masters had been left under placeholders.
• Capability catalogue: item groups, item codes, decodification, the pricing library, parties and the shared inbox are marked Live, matching those screens.
• Inbox: the list can be narrowed to messages that have an office assigned, or to messages that have none.
• Requirement gathering preview: GEMINI_MODEL replaces the default extraction model, gemini-3.5-flash-lite.

2026-10-04

• Requirement gathering preview: requirement decodification is organized into three distinct pipeline phases: source structuring that cites short source excerpts, catalogue decodification using Gemini 3.5 Flash-Lite (gemini-3.5-flash-lite) with custom value preservation for non-standard customer options, and semantic Jev verification scoring populated specification fields against exact customer snippets.
• Requirement gathering preview: decodification schemas preserve exact customer snippets and field types (including select options, numbers, ranges, text, and booleans), ensuring unstated customer requirements remain absent rather than defaulted.

2026-10-03

• Requirement verification preview: populated fields show Jev’s verdict and confidence in that verdict, not extraction accuracy. A confident mismatch does not produce a high support score.

2026-10-01

• Reading enquiries: a colleague’s reply to colleagues that says nothing of its own — empty, “PFA” or only a signature — above a client’s enquiry forwarded inside Flowtech is now read as that client’s enquiry instead of being set aside as other mail. When the client’s email is already held under the same subject, the reply is linked to it as a copy and not read again; otherwise the enquiry is read from the quoted text and, when the reply holds no document of its own other than a picture, marked as missing the client’s attachments.
• Mail processing: reading an enquiry now also notes, for each category, the likely product type, such as a glass tube or a metal tube rotameter, and a category named only by its type is read as asked for. The mail debug page shows the likeliest type beside each category.
• Mail processing: an enquiry’s categories are now also read from a short excerpt of each converted attachment — its headings, table column names and a few lines that name a product — so an email that only says “please quote as per the attached datasheet” is no longer left unresolved. The excerpt opens with each item table’s repeated values and any row stating a type, such as “Instrument Type: Reflex”, even under a title block, and a flow meter of the variable area type is read as a rotameter. Jev is told not to count a product listed only in an index or abbreviations page as asked for, and an attachment informs Jev’s answer but never marks a product asked for on its own.
• Documents: a picture attached to an enquiry, such as a photographed datasheet or bill of quantities, is now transcribed to text once the email is typed as an enquiry, while model calls are on, and marked as read from a picture. Pictures in other emails and scanned PDFs are not read, and the handbook no longer says scanned PDFs are.
• Documents: R49 and R50 now say that a picture that fails to read is asked once more straight away, then listed as not read with the reason, and that a document is otherwise tried again only when its email is processed again, which today means a developer reprocesses it. The “Retry a document that failed to read” capability is removed from the catalogue, since no screen puts one document back in the queue.
• Documents: logos and icons an email’s body shows are no longer listed as attachments that could not be read, and a document now has 30 seconds to convert instead of 10, so a document the server reads slowly is read rather than timed out.
• Requirement gathering preview: source structuring and catalogue extraction both use Gemini 3.5 Flash-Lite (gemini-3.5-flash-lite) via Google Generative AI with native structured output; failures stop the run without provider fallback.
• Requirement gathering preview: new source structures carry compact applicability markers and original-line condition references. Validation distinguishes unresolved context from applicable requirements and preserves separate conditions during compaction; these checks do not guarantee correct interpretation.
• Requirement gathering preview: source-structuring guidance separates unresolved applicability from shared requirements and keeps unrelated instrument sections and spare-part mentions from becoming installed-item specifications. Source-scope interpretation still requires verification.
• Requirement gathering preview: extraction guidance now separates scope, component and property, distinguishes design and operating conditions, and requests value-bearing evidence while retaining full requirement qualifications.
• Requirement gathering preview: an extraction with structured sources but no specification fields now stops for review, preserves its response and skips scoring instead of reporting success.
• Requirement gathering preview: shared and additional source information cites short source excerpts instead of copied passages. Standards for unrelated instruments remain reference context rather than shared item requirements. Populated specification fields use verbatim evidence excerpts of at most six whitespace-separated words; original sources and complete requirement values remain available.

2026-09-30

• Email Management: the Sync state tab now shows each mailbox’s real sync status, last run, failures and last error, refreshed every 30 seconds, instead of sample data.
• Mailboxes: while mail sync is paused, a newly enrolled or re-enabled mailbox waits for the first scheduled sync after sync resumes.
• Requirement gathering preview: the development tool keeps source-linked items and scoped shared requirements, defaults unstated quantity to 1 with an explicit default marker, and scores returned specification fields per item. Source structuring shows live estimated output-token counts and elapsed time, with at most one retry on retryable connection failures. This preview does not change production enquiry or quotation records. See requirement gathering preview.

2026-09-29

• Mailboxes: a newly enrolled mailbox, or one turned back on, now starts syncing straight away instead of waiting for the next scheduled sync.
• Mail debug: only the Developer role sees the mail debug page, its sync and model-call switches, and its menu entry. Administrators and every other role no longer do, in any environment.

2026-09-28

• Inbox: opening an email now shows it with its body, From, To, Cc and date, and the reading of an enquiry now lists the job references found in it (such as a job or enquiry number), each thing the client asks of the offer, the due date in their words, their terms documents and full contact, and who forwarded it with their note. Bodies keep their formatting and embedded pictures; pictures linked from the internet are left out, and pictures a body shows no longer appear among the attachments. Nothing in an email can run.
• Inbox: every conversation and email shows its type, and the email-type filter, now on, narrows the list to any mix of types or to emails not classified yet. An enquiry shows its due date and urgency in the list and, when opened, what its reading found: the categories asked for, the due date, how many things the client asks of the offer, the client contact and who forwarded it. A conversation is named after the client company the reading found. The Needs Review tab shows its count, and a message sent for review is labelled “Needs review” rather than “Syncing”.
• Inbox assignment: when someone else changed a message’s assignment first, saving now says so under the form and reloads the saved assignment instead of only showing a notice.
• Inbox: the Active tab lists only emails the worker has finished: classified, and, for an enquiry, labelled and read. An email still being processed no longer appears, in the list or inside its conversation, until it is finished. The Needs Review tab now lists every conversation with an email sent for review, not only those among the conversations already loaded.
• Mail debug: the feed can be filtered by email type: any of Enquiry, Revision request, Quotation, Purchase order, Sales order, Follow-up and Other, and emails not classified yet.
• Mail processing: only enquiries are now labelled and read. An email of any other kind, such as a purchase order, quotation or follow-up, is finished once it is classified; its classification is still shown.
• Mail processing: switching model calls back on from the mail debug page now picks up the emails that waited while they were off straight away, instead of about half an hour later. An email waiting its turn in a long queue is no longer sent to Needs review for taking too long.
• Mail processing: a client email that arrives again is now a copy, and not read again, only when it arrives within 30 days of the first, reached the same office, and adds nothing, and, when it was forwarded, every colleague who passed it on wrote only a greeting or filler such as “FYI” (R2a). A standard RFQ re-sent next quarter, and a forward in which any colleague writes “client now wants 20”, are read in full, and so is the same enquiry sent separately to two offices, at each office. One email addressed to both offices is still held once and read once. The client and the colleague share one list of filler, which now includes routing words such as “check”, “revert” and “look into”, so a client’s own “please check and revert” over the same files now counts as filler, and that re-send is a copy.
• Mail processing: an enquiry forwarded with our own reply above the client’s email, or sent on as a reply that quotes the client’s email under its “From” and “Sent” lines, as Outlook quotes, is now read from the client’s email, with their contact; behind our own mail the first outside sender is taken for the client, even a supplier. An enquiry with no outside sender, or a reply that quotes the client under an “On … wrote:” line, as Gmail quotes, is read whole, the colleague’s own words included, with no contact. Flowtech’s other addresses, such as a shared Gmail inbox, now count as Flowtech’s, not as a client. A number listed after “Tel” or “Mob” is no longer read as a PIN, and more PINs in Uttar Pradesh, Uttarakhand, Bihar and Jharkhand now give their state; a PIN whose first digits two states share still gives none.
• Limitations: a six-digit reference or PO Box number in a client’s signature, such as “Ref 450012”, can be read as their PIN, with a state filled from it, when it comes before the address’s own PIN or the signature has none.

2026-09-27

• Inbox attachments: previews and downloads now use short-lived download links, cached briefly while a preview is open, keep original filenames intact, and cap large text files to their first lines with a note to download the rest. S3 previews additionally need a bucket CORS rule allowing GET from the web origin.
• Global Inbox: added message assignment and triage capability. Office Heads can assign or reassign messages within their office, while Administrators and Developers can reassign across offices or clear an assignment from the right-hand action panel. Unassigned messages can be claimed into an office by authorized Office Heads or assigned by Administrators.
• Inbox: Needs Review is on. A conversation is marked Needs review, and listed on that tab, when a message failed to come in or the worker could not classify it after its retries. Drafts stay off.
• Mail processing: a client email that reaches FlowOS again and adds nothing — forwarded to a second person, or sent again with the same files and the same or no words, or, with no files on either, the same words — is now linked to the one read first and not read again (R2a). A note that is only a greeting or filler, such as “PFA” or “kindly quote”, counts as none. A re-send with new files, or with any other words, even “revised qty 10”, is read in full, and R10 applies to it. Every email processed from now on also records its origin: the client behind a colleague’s forward. Mail processed earlier has none, so a copy of it is not recognised.
• Connected systems: only what typing a message needs now goes to the language-model service: its subject, new and forwarded text, and attachment names. The lines of a message are no longer sent to it for tagging.
• Enquiries: each enquiry processed from now on records which product categories of the item group master it asks for — several where it asks for several — named from its subject, attachment names and what the client wrote. A forwarded enquiry also records who passed it on. Enquiries processed earlier have none. Shown on the mail debug page; nothing routes on it yet.
• Connected systems: naming an enquiry’s categories also uses the language-model service. Only the subject, attachment names and the client’s own words are sent; when the service is unavailable, the categories are named from the category words alone.
• Enquiries: each enquiry’s reading now also records what the client asks of the offer — delivery, price basis, payment, taxes, validity and warranty, documents, inspection, a make or model, or another instruction about the offer — when the offer is due, whether it is urgent, and which attachments are named as the client’s terms. Enquiries read earlier have none.
• Connected systems: reading what an enquiry asks of the offer also uses the language-model service. Only the client’s own lines that may ask something are sent, each with the line above it; when the service is unavailable, a line whose words name an ask, such as “delivery” or “due date”, is kept as that ask, unconfirmed, and the due date is still read from those lines.
• Enquiries: each enquiry’s reading now records the client’s contact — name, designation, company, email, phones, GSTIN and address — read from their signature. A language model splits the signature; anything it returns that the signature does not say is dropped. Enquiries read earlier have none.
• Connected systems: a second language-model service, the contact reader, reached over an OpenAI-compatible API (DeepInfra today), now splits each enquiry’s client signature. Only the signature and, for a forwarded email, the client’s header lines are sent; when it is unavailable, the contact keeps what rules read and is marked as read by rule only.
• Connected systems: the language-model service, TypeSafe’s Jev, is now reached through TypeSafe’s own service rather than through a gateway. What is sent to it is unchanged, and it is kept under TypeSafe’s default terms, with no zero-retention agreement yet.

2026-09-26

• Inbox attachments: operators can preview supported email attachments and download the original file from the message view. Access follows the same inbox permission and mailbox scope as the message.
• Inbox message visibility & search: conversation threads and message details now gate display to extraction-ready messages, keeping pre-extraction and failed intake staging internal to diagnostics. Added real-time debounced search across conversation subjects and senders.

2026-09-25

• Item Master: in a family priced by flow range, the price bands of an item code can now be copied from another code in the same family. Copy From, beside the flow unit, lists the family’s other codes that have bands; picking one fills in its bands’ ranges and prices and its flow unit, ready to edit before saving. Over bands already entered it asks first, then replaces them. A band whose range and unit stay the same keeps the Pricing Library rates priced against it.

2026-09-24

• Global Inbox: shared triage surface is now live at /inbox for inbound customer inquiries delivered through Microsoft Graph delta streams. Automatically groups incoming emails into conversation threads, links senders to Customer Master parties, enforces office and employee mailbox scoping across all reads, and provides direct launchpads to the quotation workspace.
• Mail Intake & Ingestion: Microsoft Graph delta synchronization is now live (@flowos/mail), staging delta changes to a durable Postgres ledger before advancing cursors. Added BullMQ queue processors for downloading raw RFC 822 MIME blobs and attachments with $value fallback, robust retry semantics with exponential backoff, dead-letter recording, and basic auth protected queue monitoring under /queues. Includes safe per-mailbox delta reset tooling with shared message isolation.

2026-09-22

• Pricing Library: a library value can now be deleted once no datasheet’s current version uses it, even if older published versions still do. Before, every version ever published counted, so a value could never be deleted after its first use. Deleting keeps the value’s name as plain text on the options in older versions, deletes the prices recorded against it in those versions, and archives a copy of everything removed. If a current version does still use it, the dialog lists the item groups and rows to take it off before publishing, and any current prices to delete. Deactivate instead hides a value from the option picker without deleting it.

2026-09-21

• Datasheet editor: the options on a select header can now be reordered — drag an option by the grip at the left of its line, or use the keyboard. Only the order the menu reads in changes; codes, defaults and prices stay as they are. Components lists are not reorderable yet.
• Party Master: added Credit Terms support to Party records with a Credit Allowed permission toggle and configurable Credit Days limit (e.g. 30, 45, or 60 days). Includes reactive credit fields in the create/edit modal, Credit badges in the main Party Master table and company locations directory, and automated DTO serialization.
• Commercial: Terms & Conditions (T&C) Master delivery options simplified to static standardized options (Within Gujrat, Within India, Outside India). Default delivery destination selection is merged directly into the Default Payment Terms card, and sequential price rules require an explicit delivery destination with interactive preview simulator support.
• Sales Office Master: upgraded /master/offices into a full view-only directory with office codes, regional zones, locations (city, state, address), contact details (email, phone), active/inactive status, and assigned employee counts. Includes search, zone and status filter controls, and a slide-over view drawer displaying office contact details and assigned team members.
• User Management: users can be provisioned without an office and later assigned, transferred, or unassigned by an all-office administrator. These changes are recorded in the access history.

2026-09-20

• Commercial: Terms & Conditions (T&C) Master updated with compound Price + Geography rules and standardized delivery options (Within Gujrat as default, Within India, Outside India). Sequential payment milestone rules can target specific delivery destinations or all locations with live quotation preview and interactive simulator support.
• Handbook: Decodification Master is now a group in Features, holding the Decodification Master, How answers are decided and Pricing Library pages. Three interactive diagrams sit on them: from draft to a published version, how a header’s answer is decided (the five steps, the if / else-if / else of Decided by, and which default wins), and the four ways an option can be priced. Each has a preview that opens the full diagram. How answers are decided and Pricing Library moved into the group; their old addresses redirect.
• Item Group Master: each row now has an eye button that opens the family read-only, with three tabs — its item codes, its current datasheet (laid out as the Decodification viewer lays it out, with the unit price across sizes and each price-driving option’s add-on beside it — one figure, or a range such as +₹1,500–₹3,500 when it differs by size — plus an Edit datasheet button for those allowed to edit) and the rules recorded against it. The header gives the category, series prefix and the code the next release would take. Anyone who can see the list can open it.
• Item Master: each row now has an eye button that opens the code read-only — its model number and datasheet, HSN, unit, measuring range, unit price or price bands, and any options it answers differently from its datasheet. Anyone who can see the list can open it; editing still needs the edit permission.
• Handbook: a new page, “How answers are decided”, under Features next to Decodification Master. It lists every way a header gets its answer — Gate, Inherit, Decided by, hard limits and conditional defaults — in the order they apply, with a worked example of each and a chart for choosing between them.
• Datasheet editor: a “Decided by” mapping can now depend on more than one header. Add condition puts an AND line in a mapping, between its IF and THEN, to require another header’s choice as well; the mapping applies only while all its conditions hold, and pairs it does not name fall through to the header’s own default. A pair a broader and a narrower mapping both answer needs exactly one Default, and the editor names it. When an item code is edited so that one of the deciding headers sits at a choice no mapping names, the mapped header returns to its own default, unless it is set by hand on that code. (R60)

2026-09-19

• Product Limitations & Flow Sizing: live master screen at /master/limitations. Provides full lifecycle management for limitation and restriction rules (operational limits, design limits, suitability gates, mandatory accessories) scoped to product families or specific item codes. Automatically derives engineering measurement units from chosen process parameters, and includes reference flow-sizing bands by fluid phase and pipe size with CSV exports and active rule toggling.
• Decodification Master: process factors now separate hard limits (an option outside them cannot be supplied) from conditional defaults (ordered rules that pick the default, first match wins). Factor-value stars became conditional-default rules. The preview takes a range for a numeric condition and reports a requested option that breaks its limit.

2026-09-18

• Item Master: moving an item code to another item group now gives it the next code in that family’s series and that family’s datasheet, instead of keeping the old family’s code; rates citing the old code follow it. A move is refused while the code answers options differently from its datasheet, carries price bands the new family cannot take or that have rates, or when the new family is inactive or has no active datasheet. IBR vortex flowmeters are their own family, IBR Vortex Flowmeter (prefix IBVF), with their own datasheet: the 13 IBR codes move out of Vortex flowmeter and are renumbered FIBVF0000001–FIBVF0000013.
• Item Master: every existing item code is renumbered into its family’s own series — F, the item group’s prefix, then a running number from 1, in the order of the old codes (FACBR0000001 becomes FABRM0000001). The item keeps everything else, including its prices, and a rate’s source item follows the new code. The old ERP numbers are no longer shown, and the item groups list and export drop the ERP Group Code column.
• Item Master: a new item code is numbered from its item group’s prefix — F, the prefix, then a seven-digit running number (FABRM0000016) — instead of continuing the ERP stores group’s series. Each family has its own run, so a family the ERP never grouped can now release codes, and two families no longer share one run. An item group’s prefix must be 2–6 capital letters, and the server now refuses to change it once the family has codes, as the screen already did.
• Item Master: price bands now run back to back in one flow unit. The unit is chosen once for all of a code’s bands; only the first band’s lowest flow is typed (it may stay open), and each later band starts where the one before it ends, so bands can no longer overlap or leave gaps. A banded code’s measuring range is no longer typed separately — it is the span of its bands and follows them. A measuring range may now leave its lowest flow open, and flows may be negative.
• Item Master: in a family priced by flow range — acrylic body, metal tube and glass tube rotameters — a new code, or one with no unit price yet, now opens on By flow range with its price bands, instead of on a single price. A code that already carries one unit price still opens on it.
• Commercial: Consolidated Party Group management directly into Party Master with a company-wise checkbox view toggle. Industry sectors are now dynamically derived from active customer parties. Added inline company creation via searchable combobox in the Add Party modal, and contextual sector-based GSTIN quick selection.
• Commercial: Refactored Party Master into a two-tiered unscoped master model (PartyGroup for corporate entities, and Party for multiple office/plant delivery locations). Added automatic company name capitalization normalization, GSTIN combobox with strict 15-char validation, and duplicate detection with confirmation workflow.
• Commercial: Terms & Conditions transitioned to a global catalogue master with tiered sequential payment price rules, delivery options management with default and deactivation invariants, and idempotent non-destructive seeding.
• Pricing Library: in a family priced by flow range, a rate table splits a size into one column per price band — the size above, its bands beneath — and each band carries its own rate. Set multiple lists bands alongside sizes, and the priced count covers every band. The datasheet preview shows such a code as one column per band, priced by the band, and the datasheet editor’s price info lists each band with its price. A band without a rate adds nothing rather than borrowing the size’s rate.
• Item Master: in a family priced by flow range a code can carry price bands — one price per flow range at its size — instead of a single unit price; the form asks which. The list shows such a code as its price range and band count. Acrylic body, metal tube and glass tube rotameters are priced this way, and any item group can be switched to it from its edit form. The code’s own flow range is now called its measuring range, to keep the two apart. Flow fields also accept decimals such as 0.003, which the form previously refused to save.
• Item Master: a code can now carry the flow range it reads — a lowest flow, a highest flow and a unit, entered together or left out entirely. It shows as its own column in the list. Rotameters and the other flow meters are chosen by the duty they must measure rather than by bore alone, so this is what says whether a size suits an enquiry. 59 codes arrive with ranges already filled from the client’s published sizing tables: metal tube rotameter, turbine, electromagnetic and oval gear. Every other family starts empty and can be filled in or corrected later.
• Item Master: the 12 metal tube rotameter codes the ERP already carries (15NB to 200NB) are now in the catalogue. They were held back because the family was set to vary by F/F length — a two-option dimension — while the ERP’s codes vary by line size, as they do for every other rotameter family. The family now varies by line size; F/F length stays a question on the datasheet. Where one line size sells at several prices, those are price bands on the one code.
• Catalogue set-up: re-running the catalogue import no longer removes item codes that are absent from the client’s ERP export. Codes released in the app are kept, and the import reports how many it kept.

2026-09-17

• Commercial: Party Master now supports full lifecycle management (create, edit, delete) for office-scoped customer records from the toolbar and row actions, including company, buyer, billing, consignee, GSTIN, and sector details.
• Item Master: search now matches each word separately, in any order, and ignores spaces and punctuation — bypass 125nb finds “By-Pass Glass Tube Rotameters 125NB”, which previously needed the name typed exactly. Closer matches are listed first — a name starting with what you typed beats one carrying the words further in. Search still covers the name and item code, not the model number.
• Lists: the edit, view, copy and delete buttons on each row are now always shown instead of appearing on hover, as icons named by a tooltip — the pencil is always Edit and is outlined. On Decodification Master, the eye button (view) sits in the first column.
• Pricing: an option’s price can now be negative (it lowers the price) or zero (priced, adds nothing), in the Pricing Library and in the datasheet editor’s Pricing section. The price preview shows a negative add-on as − ₹ and subtracts it from the total. Item unit prices still have to be positive.
• Datasheet preview: the editor’s Preview and the list’s eye button now price a datasheet at every size — unit price, each Driver row’s add-on, and the total — and work as a configurator: switching a menu or an enquiry condition re-runs Decided-by mappings, parent-header gates, inheritance and process factors (a header moves to the option starred for a Fluid Type, say). Anyone who can view datasheets can use it; nothing is saved.
• Datasheet editor: when a header’s default does not suit a Fluid Type value that several options suit (Solid, with SS 304 for Liquid and Gas as the default), one of those options is starred as that value’s default, on its chip. A note above the options lists each such value and its starred option, and publishing is refused until each has exactly one star. The publish review marks a starred value with ★. (R61)
• Datasheet editor: the publish review now lists a change to an option’s process factors — its Fluid Type values, or its Size band — which it previously left out, and names a header’s process factors instead of showing their internal keys. The limitations page records how defaults are planned to work once process factors are evaluated: each option markable as the default for a factor value.
• Item groups: a family that still has datasheets can now be deleted. The confirmation says how many datasheets it has and that they are deleted with it, along with every published version and price. Deleting is still refused while the family has item codes, and while any item code uses one of its datasheets. Any other family that used one of those datasheets as its current datasheet is left without one. Previously this failed with a server error.
• Datasheet editor: Fluid Type (Solid, Liquid, Gas) joins the process factors, and each option can state which fluid types it suits — FLANGE TAP DEGREE’s 90° for gas and 180° for liquid can now be recorded. New values can be added from the editor and reach every datasheet using the factor. A field can now be answered as Options, from a list kept in the row library, and a new process factor can be created as options too. Nothing filters menus by process factors yet.
• Datasheet editor: process factors now come from a shared list of process variables instead of free text. Size (NB) is new, alongside operating pressure and temperature, flow, density, viscosity, conductivity and pressure range. A missing factor can be created from the picker, or an existing field made one, and a name already on the list is offered rather than duplicated. Each option states an exact value or a min–max band for a numeric factor. Factors typed before the change still show, marked legacy. A Yes/No field’s default is now chosen from Yes / No, and a text default can span several lines.
• Datasheet editor: a “Decided by” mapping now names an allowed answer, not only a default, and the setting reads Allowed answers. A choice several mappings name allows each of their answers, with one marked Default — Non-IBR allows CS and SS 316 with CS the default, while IBR allows CS only. Publishing is refused until each such choice has exactly one default, replacing “the later one wins”. Item codes offer only the allowed answers in their standard configuration, and saving one refuses an answer its mappings do not allow. (R60)

2026-09-16

• Commercial: Terms & Conditions Master screen live at /master/terms, providing office-scoped defaults for packing charges, warranty duration, milestone payment term allocations (with strict 100% total invariant), and delivery options management with instant preview.
• Commercial: HSN Master screen live at /master/hsn, providing full statutory classification management with split CGST/SGST/IGST rates, ERP General Ledger accounts, search/filter, CSV export, and CRUD controls.
• Item Master: several item codes can now be deleted at once — tick them, or the whole page, and choose Delete. Codes with limitations are kept and counted in the result. Deleting remains for codes released by mistake; a used code is still retired instead.
• Decodification Master: a datasheet can now be deleted from the list, by anyone allowed to delete catalogue items. Deleting is refused while item codes use it — archive it instead — and the confirmation states the versions and prices that go with it. Deleting a family’s current datasheet leaves the family without one and clears which of its headers drive price.
• Decodification Master: a new datasheet can start as a copy of a published one (Copy From, when adding a master), and the editor’s Import rows adds chosen rows from any other datasheet to the draft. Rows, options, letter codes, parent links and Decided-by mappings come across; a row whose key is already taken is renamed, and a row whose parent was left out becomes independent. On publish, which headers drive price is copied onto headers the family has not reviewed yet; prices themselves are never copied. Corrected the catalogue set-up guide, which still said publishing does not point the item group at its first master.
• Datasheet editor: a header can now be answered from another header’s choice, under a new “Decided by” setting. Each mapping names the deciding choices that lead to one answer, so several choices may lead to the same one — the case Gate and Inherit could not express, since those match a single choice to a single outcome. The editor names any deciding choice no mapping covers, and any two mappings that disagree. Mappings the datasheet already carried, such as the tubular level indicator’s cage material deciding how its scale is marked, are now visible and editable instead of only readable in the seed. A mapping fills the answer in and does not remove the others from the menu; a released item code keeps whatever it was released with.
• Item codes: the release form is now read as three collapsible bands, each summarising itself — the code and name, the classification and price, and how far the standard configuration has drifted from the datasheet. The composed model number and the datasheet it came from are stated together rather than sitting in a disabled box, required fields are marked, and Cancel and Save stay in view while the form scrolls. The HSN picker now states the GST rate each classification attracts. Standard configuration lays its rows out to the width available instead of always two across, and a long answer no longer overflows into the next column.

2026-09-15

• Item codes: the standard configuration now applies the datasheet’s own rules — choosing MS wetted parts fills the scale in as acrylic, and says which answer drove it. The model number is composed the same way the ERP import composes it, so a code released here matches its siblings in the family. Menus that mark two defaults because a rule picks between them no longer block publishing.
• Item codes: Model Number is now read-only while releasing a code — it is composed from the family’s datasheet and the standard configuration, and changing it means changing one of those. Where a position’s menu marks no default it cannot be composed and is left out; the screen now says how many are missing, and the code records the count instead of reporting itself complete. Changing the item group now recomposes the model number, the item code and the name, and clears standard-configuration answers belonging to the previous family.
• Item codes: releasing a code now generates its number instead of asking for one, continuing the ERP series for the family’s stores group from the highest number already in it. Where the ERP groups two families together they share one run of numbers. A family the ERP does not group still asks for the number outright, since there is no series to continue. An item whose variant duplicates one already released now says so, instead of reporting a duplicate code.
• Decodification Master: a menu now marks at most one option as the default — picking one clears the previous, and picking the current default again leaves the menu with none. Publishing is refused while any menu marks two, naming the rows to fix; masters authored before the rule keep working until their next publish. Component lists are unchanged, and may still supply several parts at once.
• Datasheet editor: a row’s Visibility can now name the parent choices it applies to, not only hide the row when the parent is “Not Applicable”. That is what lets two or more rows split one header between them — where a parent’s options are real alternatives priced differently, each alternative gets its own row and only the one that applies is asked. The parent’s options list shows which rows each choice brings into play, and warns about a choice no row covers.
• Decodification Master: a driver row’s options can now be priced right on the row, in a Pricing section beside the Priced by… choice — the Pricing Library is no longer the only place to enter a rate. A row authored or re-based in the current session needs publishing before its price can be set, the same rule that already applies to marking a header Driver; a row you haven’t touched this session prices immediately.
• Commercial: Party Master screen live at /master/parties, displaying registered customer companies, buyer and consignee addresses, GSTIN, and industry sector under ambient office scoping.
• Pricing Library: overwriting a price now needs edit rights, separately from the create rights that enter a first one; someone holding neither sees the figures read-only instead of an input that fails on save. Size columns now read in size order (DN8, DN15, DN100) rather than alphabetically. A price entered here against no specific item records that, instead of filing the size as an item code.
• Decodification Master: the editor now carries the item group’s own item codes and their unit prices across the top of the datasheet, read-only, so the base an option’s price is added to is visible without leaving the screen.
• Pricing Library: a price form now shows its Save button at all times, greyed out until the figure has changed and reads as a valid amount, instead of revealing one only once an edit is under way. Every figure already priced now states who last set it and on what date.

2026-09-14

• Datasheet editor: a row’s parent-header settings now read as sentences — “Depends on” names the parent, “Visibility” chooses between “Hide this row when is <its N/A option>” and “Always ask this row”. Hiding is unselectable until the parent carries an option marked “Not Applicable”, and a parent that is named but drives neither visibility nor material now says so.
• Datasheet editor: a group now takes its first published master as its current one, so price relevance can be set on a newly authored datasheet; marking a header a Driver before publishing it now says why instead of appearing to work.
• Datasheet editor: saving a datasheet that has not changed no longer records a new version. An option whose pricing-library link cannot be resolved now reads “link broken” instead of “no price set”. Corrected the EARTHING MOC and SWITCH DETAILS worked examples on the Decodification page.

2026-09-10

• Decodification masters: a header can now name process factors, a parent header (gated and/or inherited independently of each other, inheriting narrowable to specific parent options), and options that mean “not applicable”.
• Decodification Master: a driver row’s charge method (fixed amount, by parameter, rate table, or base variant) is now chosen per option, with a live hint showing what’s actually been priced in the Pricing Library.

2026-09-08

• Pricing Library: removed the approval step — setting a price now takes effect immediately, one rate per price key, latest entry wins. Pricing reshaped around each item group’s driver rows instead of a flat, value-level price.

2026-09-07

• Roles: added a Pricing Library permission (view / create / edit / delete / approve) to the role editor, covering the option library and option-rate approval workflow.

2026-09-04

• Handbook: opened in FlowOS, structured after the Flowtech process register: overview, capabilities, roles, glossary, lifecycles, rules, automatic behaviour, connected systems, limitations, workflows and features. Written for the complete product — login, offices, mail, catalogue, quotations, orders, ERP — not the proof of concept.