Interior Fulfillment Studio: How to Manage Materials, Samples, Prices, and Purchases Across Multiple Projects

While a designer is handling one project, much can be kept in mind: SKUs sit in one spreadsheet, prices live in a chat with the manager, and samples sit on a single shelf. Once there are five, ten, or twenty projects, this scheme falls apart. The same moulding starts being called different things in different files, an old quotation is treated as the current price, a sample has gone to one client but is needed by another, and the supplier receives several versions of the same specification.

From this point on, procurement stops being just about selecting beautiful products. It becomes the management of data, statuses, timelines, and physical objects. An interior procurement studio must see the project portfolio, the central SKU database, the sample library, current prices, RFQs, quotations, orders, deliveries, claims, and closing data all at once.

At the same time, roles need to be separated. The studio or procurement specialist organises the process: selects, approves, builds the specification, manages the budget, requests prices, and controls purchasing. In this system, STAVROS is the manufacturer and supplier of specific materials and decor: mouldings, wall panels, stucco and carved decor, furniture hardware, samples, and technical files. Calling STAVROS a "procurement studio" would be incorrect.

The working chain for a multi-project studio looks like this: project portfolio → central catalogue → project spec → samples → prices → RFQ → quotations → client approval → purchase order → production → delivery → acceptance → claim → project closure → knowledge base.

Bar Stool STU-006

from 784.15 $

Bar Stool Hygge 003-002

from 917.12 $

Stool Frame STU-005

from 725.23 $

Chair Frame STU-004

from 957.74 $

Chair Archie 003-003

from 962.26 $

STU-009 bar stool

from 770.37 $

Hygge Bar Stool 003-004

from 782.20 $

Interior rail RK-002

from 12.32 $

Go to Catalog

A procurement studio and a materials supplier are different roles

Separation of responsibility is the foundation of the entire operating system. If it is blurred, the supplier starts making design decisions, and the procurement specialist starts making assumptions about a product that the manufacturer should be confirming.

Watch video ...

What the procurement studio is responsible for

• selecting product solutions to match the design project;
• approving specific items with the designer and the client;
• building the project specification;
• maintaining the budget and change history;
• requesting commercial proposals;
• approving the purchase and schedule;
• monitoring deliveries and closing project items.

Our factory also produces:

Wooden Molding K-011

from 8.66 $

Wooden Batten K-020

from 5.25 $

Wooden molding K-070

from 10.13 $

Wooden molding K-074

from 15.25 $

Wooden Moulding K-079

from 11.47 $

Chair frame STU-007

from 1,626.25 $

Versailles Chair 003-001

from 2,022.11 $

Hans 004-002 Chair

from 1,241.61 $

View Full Product Catalog

What the supplier is responsible for

• the specific SKU and its current product configuration;
• material, size, and available finishes;
• the current price or the price of a specific commercial proposal;
• availability and production lead time;
• samples, if available;
• product technical files;
• production, assembly, and shipment of the order.

This distinction is especially important in the commercial section of the article. The queries “interior assembly service” and “distinct design project cost” refer to the studio's service, not to the STAVROS product range. STAVROS participates in the article as a source of specific product items, samples, technical data, and commercial terms for its products.

Why working on five projects requires a different system than working on one

In a single project, an error is usually local: an incorrect price ended up in one estimate, a sample was lost in one folder, one SKU had to be double-checked. Across a portfolio of projects, the same error multiplies.

For example, one molding is used in three projects at once. In PROJECT-A it is selected in oak, in PROJECT-B in MDF, and in PROJECT-C in beech. If the database stores only the name “STAVROS molding,” the system is already ambiguous. If, in addition, each project contains a separate copy of the product card with its own outdated price, then two months later no one knows where the current data is.

Multi-project work adds several more dimensions:

• identical SKUs are simultaneously present in different projects;
• prices for one item were obtained on different dates and for different volumes;
• one physical sample is needed by several teams;
• deliveries go to different addresses;
• project stages differ;
• responsible managers are different;
• some items are already ordered, some are still being approved;
• for one product there are several commercial proposals.

That is why a good interior procurement studio manages not files, but entities: project, product, sample, RFQ, proposal, order, delivery, claim. Excel can be a tool, but the logic must exist independently of any specific program.

The studio's central catalog and the project specification are not the same thing

This is one of the most important distinctions. The central catalog is the studio's knowledge base. It stores all verified products that the team can actually work with. The project specification is only a selection of products related to a specific object.

If these levels are mixed, each new project starts generating duplicates of the same cards.

The central database should not try to store "usually 80 meters are needed". Quantity always belongs to a specific project. However, the article number, link to the product card, 3D, DWG, and sample ID are convenient to store once.

For STAVROS, the central library can be built starting from the main catalog, and then the items can be distributed across real product groups: wood and MDF, moldings, panels, stucco, carved decor, and furniture hardware.

One SKU must have one master card in the studio database

A bad library quickly fills up with lines like these:

beautiful molding
Stavros molding
oak molding
molding from the Petrov apartment project
that molding from the showroom

This may be the same product. Each real item must have one master-card, and project records must reference it.

Minimum master-card fields:

• manufacturer;
• exact SKU;
• category;
• available materials;
• dimensions and product lengths;
• clean card URL;
• links to 3D and DWG;
• sample ID of the physical sample;
• status ACTIVE / ARCHIVE;
• last check date.

If an item has been replaced or is no longer in use, it is better to archive the card rather than delete it. Old projects must retain a historical link to the actual SKU.

Material is part of a specific configuration, not a comment on the SKU

If the same profile is available in oak, beech, and MDF, that is not one purchasing line. For a designer, the shared profile may be one object, but for purchasing, each materialization is a separate configuration.

Working note:

MLD-___ / OAK / size ___
MLD-___ / BEECH / size ___
MLD-___ / MDF / size ___

Why this matters: material can change the price, available length, finish, and production lead time. In one project, oak may be approved as a natural accent, while in another, the same profile in MDF is for painting. If the database stores only a generic item code, commercial and design data begin to mix.

For STAVROS mouldings, the working source may be mouldings section, while the general product database for wood and MDF is wood and MDF products section.

The sample library must be tracked like a small warehouse

A physical sample is a resource with a location. If a studio has ten projects, the system of "samples are somewhere in a cabinet" stops working. One sample may be needed by several teams, but physically it can only be in one place at a time.

For each sample, it is useful to store:

• its own code;
• the SKU it belongs to;
• the material;
• the size or type of the sample;
• current status;
• physical location;
• who took it;
• for which project;
• issue date;
• expected return date.

The current STAVROS catalog includes a separate product samples section: moldings, wooden baguettes, rosettes, slatted panels, and display stands. For the studio, these are not just demonstration products, but physical units that make sense to put on the books.

How to code samples

A good sample ID should be unique and at the same time readable. For example:

SMP-STV-MLD-014-OAK-01

Where SMP is the sample, STV is the supplier, MLD-014 is the SKU, OAK is the material, and 01 is the number of the physical item. If the studio has two identical samples, they receive different last numbers.

The sample code does not replace the product SKU. It identifies the physical item within the studio. This allows you to have multiple copies of the same SKU and know where each one is.

One sample can work on several projects, but only one at a time

For a sample library, it is useful to standardize statuses:

• IN LIBRARY — available;
• WITH DESIGNER — with an employee;
• WITH CLIENT — handed over to the client;
• ON SITE — located at the site;
• RETURN EXPECTED — return expected;
• ARCHIVE — no longer used as a working one.

If two projects simultaneously want the same sample, the system should show a conflict before an employee promises it to the client. In practice, you can either coordinate a queue or order a second copy if the category is used regularly.

This is a minor operational detail, but it is precisely from such details that the quality of interior furnishing in a multi-project studio is built.

The digital library and the physical library must be linked

A digital product card should contain a photo, SKU, dimensions, material, 3D, DWG, a clean URL, and the physical sample number. Then a designer, seeing the item in the database, immediately understands whether a real sample exists and where to find it.

Feedback is also important. A label or QR code can be placed on the physical sample that leads to the digital master card. An employee takes the sample from the shelf and immediately sees the technical data, the projects in which it has already been used, and the current status of the product.

If the digital and physical libraries exist independently, they quickly diverge: the file says the sample is available, but it has long been with a client; the sample sits on a shelf without a clear SKU; the old label does not match the updated card.

How to work with 3D and DWG without a "final_new_2" folder

STAVROS has an official section catalogs, 3D and DWG, as well as a professional page for designers and architects. For the studio, it is important not just to download files, but to link them to the master card of a specific product.

Working connection:

SKU → 3D → DWG → product card → sample ID

It is preferable to build the file name from the item code. For example:

STAVROS_MLD-014_3D_v01.max

If the studio rebuilt the model from a drawing itself, this is recorded as a studio-generated model, and the official source is stored separately. The visualizer must not arbitrarily change the scale of the actual product profile just because it looks better in the frame.

A price without a date is not a price

One of the most expensive configuration mistakes is storing a number without context. A record PRICE = 3250 ₽ is almost useless after a few months.

Need at least:

3250 ₽ / date / source / quantity / finish / project

The price depends on what exactly is being compared. A catalog price is one thing. A price in a commercial proposal for a specific volume is another. The price of an already confirmed batch is a third.

Catalog price

Used as a reference at the selection stage. It must be rechecked before the client budget and order.

Project price

The price obtained in an RFQ for a specific project, volume, and date. It must be linked to the commercial proposal number.

Price of a specific batch

The actual cost of the ordered configuration. It already relates to the purchase order and should be used in the closing financial history of the project.

How to keep a price history for a single SKU

Instead of a "current price" field, it is more useful to store a history. Then, six months later, the studio does not mistake an old cost for the current one and at the same time sees how the item behaved in previous projects.

The article should not include made-up real prices. The value of the table lies in its structure. Specific values come from the current product card or the supplier's commercial offer.

How to create an RFQ — a request to the supplier

An RFQ must describe a specific procurement need, not a project topic. The phrase "calculate the decor for the project" shifts the work of reconstructing the specification onto the supplier. A good request can be processed without additional guesswork.

Minimum RFQ contents:

• project code;
• procurement need revision number;
• SKU;
• material and finish;
• size or product length;
• quantity;
• desired ready date;
• delivery address or city;
• whether a sample is needed;
• availability inquiry;
• repeat batch lead time inquiry;
• special packaging or splitting requirements.

If an RFQ relates to multiple STAVROS categories, they can be sent in a single structured file, but each line must remain unambiguous. For example, wooden molding, slatted panel, and polyurethane overlay must not be combined under a generic "decor" line.

In the project portfolio, it is convenient to assign each RFQ its own identifier: PROJECT-A_RFQ-03. Then the supplier's response can be linked specifically to the quantity version that was requested.

One RFQ — one version of the procurement requirement

The most dangerous habit is to open an old Excel file, change the quantity, and send it again under the same name. A week later, there are three files in the correspondence spec_final.xlsx, each with different numbers.

When the requirement changes, a new version is created:

RFQ-01 — original request
RFQ-02 — panel material changed
RFQ-03 — quantity clarified after measurement

The old RFQ is not deleted but receives the status SUPERSEDED. A commercial proposal must also be linked to a specific request version. If the supplier sent a price for RFQ-02, but procurement is already on RFQ-03, the total amount cannot be transferred without line-by-line reconciliation.

Such control is especially important when a design project specifier is simultaneously communicating with multiple suppliers and clients. The revision number removes dependence on memory and the timing of a message in a messenger.

How to compare commercial proposals

The phrase “supplier A is cheaper” only makes sense after verifying that the proposals are truly comparable. Two line items may have the same product name but different material, length, finish, packaging, or lead time.

Before comparing, verify:

• whether the SKU is the same;
• does the material match;
• whether the size or product length is the same;
• whether the quantity is the same;
• whether the required finish is accounted for;
• whether delivery is included;
• what the production and readiness timeline is;
• whether there are substitutions;
• what the price validity period is;
• what the payment terms are.

A proposed alternative must always become a separate line item, not silently replace the original position. If the supplier offers a different molding instead of the selected one, the designer must verify the geometry and visual match before commercial comparison.

Such a comparison turns the quote into structured data and reduces the risk of mistaking a lower amount for a better offer, even though mandatory parameters are excluded from it.

Cost of design project furnishing: separate the studio's service from the cost of goods

The query "cost of design project furnishing" often conflates two different amounts. The first is the cost of the studio's professional service: selection, specification, supplier requests, coordination, order and delivery control. The second is the cost of the goods themselves.

It is useful for the client to see them separately:

STAVROS in this budget belongs to the block of product items and related delivery terms. The company should not be described as a provider of interior procurement services.

This distinction is also useful for the studio itself. If the procurement specialist's fee is hidden inside the "markup on materials," it is harder for the client to understand the scope of the service, and for the studio manager to assess the real profitability of the team's work.

Interior procurement service: what the client should understand before work begins

The interior procurement service is not a promise to "buy everything instead of the client" without rules. Before work begins, it is useful to establish which functions the studio performs and which decisions remain with the client.

A typical structure may include:

• selection of products according to the approved design;
• preparation and maintenance of the specification;
• organization of samples;
• requests to suppliers;
• comparison of commercial offers;
• approval of costs and substitutions;
• processing of the purchase;
• monitoring of production deadlines;
• organization of delivery;
• handling of claims;
• closing documentation.

If some functions are not included in the studio's contract, this also needs to be shown. For example, a procurement specialist may coordinate delivery but not personally receive goods on site. Or the studio may handle only selection and RFQ, while the client pays directly.

The more precise the boundaries, the fewer conflicts at the "I thought this was included too" stage.

How to build a project procurement calendar

Lead time alone is not enough. Each product line must have at least four control dates:

• SELECT BY — the deadline by which the item must be selected;
• APPROVE BY — when the client must approve it and the sample;
• ORDER BY — the deadline for placing the order;
• NEED ON SITE — when the material is physically needed on site.

If the item requires production, a production lead time, logistics buffer, and acceptance time are added between ORDER BY and NEED ON SITE. If the item is in stock, the path is shorter, but the order date must still account for delivery and the possibility of availability changes.

It is better to build the project calendar not as one general chart, but by key product items. Skirting, paneling, and a rare decorative trim can have completely different lead times.

The order date is calculated backwards from installation

Useful model:

installation ← delivery ← product availability ← production ← sample approval ← selection

That is, the process does not start with the "5–10 days" timeframe in the product card, but with the date when the product must be on site. The actual stages and internal approval timeframes are subtracted from it.

An example not tied to a specific product. The material is needed on site on December 1. Delivery and acceptance require, say, a few days, production is a timeframe confirmed by the supplier, before that a final RFQ and payment are needed, and before the order the client must approve the sample. If the sample has not even been selected yet in mid-November, the calendar already shows a risk.

This way the studio sees the problem in advance, rather than after the message "the product won't make it in time."

What to purchase earlier

What requires attention earlier is not the "most expensive" items, but items with a long decision-making chain.

These usually include:

• items with a production timeframe;
• large batches;
• complex wall panels;
• rare one-off decor;
• non-standard executions;
• items requiring a physical sample;
• elements that other drawings depend on.

Standard stock items can come later if availability and lead times are confirmed. But the specific schedule is always built around the current SKU, not the general category.

How to avoid mixing identical SKUs from different projects

The same profile can go into several projects at once. The problem arises when the studio only sees the combined order.

For example:

PROJECT-A / MLD-___ / OAK / 42 strips
PROJECT-B / MLD-___ / MDF / 18 strips
PROJECT-C / MLD-___ / BEECH / 30 strips

Even if it is convenient for the supplier to produce them side by side, within the studio these are three different needs. They have different budgets, clients, addresses, and payment statuses.

After placing an order, each line must retain the project code. It is not allowed to turn multiple client orders into an unnamed general warehouse stock if clients have paid for specific items.

A product can be reused across projects as knowledge, but not as someone else's reserved stock

The studio can repeatedly use accumulated experience: a proven SKU, DWG, 3D, sample, manufacturer information, installation notes. This is why the central catalog has value.

But it is not allowed to automatically carry over:

• the old price;
• past availability;
• the old production lead time;
• material remaining stock paid for by another client;
• commercial terms of a past project.

Historical data is useful as a reference point, but not as a promise to a new client.

Procurement statuses must be the same across all projects

If one manager writes "approved," another writes "can purchase," and a third writes "in progress," the manager cannot compare projects. A unified vocabulary is needed.

For example:

SELECTED
SAMPLE ORDERED
SAMPLE RECEIVED
APPROVED
RFQ
QUOTED
CLIENT APPROVED
ORDERED
IN PRODUCTION
READY
SHIPPED
RECEIVED
CLOSED

If necessary, HOLD, CLAIM, and CANCELLED are added. What matters is not the number of statuses, but the same meaning for all employees.

A unified vocabulary turns the portfolio into a manageable system. Interior procurement specialists can handle different projects, but the manager sees them in one language.

Procurement studio dashboard: what a manager really needs

A manager doesn't need to read every specification daily. They need exceptions: what awaits a decision, where a deadline is approaching, what is delayed.

Useful indicators:

The dashboard does not replace the database. It only shows its critical states. If a metric cannot be opened down to a specific project line, it quickly turns into beautiful but useless statistics.

How to organize delivery to different sites

Ordering and delivery should be linked but not mixed. One purchase order can have several deliveries, and several orders can travel in one vehicle if this is agreed.

The delivery card should store:

• project code;
• purchase order;
• address;
• contact at the site;
• available receiving window;
• number of packages;
• zone or floor;
• person responsible for receiving;
• special conditions for long-length items or large panels.

These details should not be kept only in a messenger. If the driver calls another employee or the delivery is rescheduled, the information must be available to the entire project team.

Before sending, the conditions must be checked against the current section payment and delivery STAVROS.

Receiving must close a specific purchase order

The RECEIVED status cannot be set simply because the truck has arrived. It means the delivery has been checked against the order.

Minimum verification:

• SKU;
• the material;
• size or length;
• quantity;
• visible damage;
• compliance of packaging units;
• discrepancies with the purchase order.

If the delivery arrived partially, the order is not closed in full. The line should show ORDERED QTY, RECEIVED QTY, and OUTSTANDING QTY.

This is especially important for project material supply, where a few missing planks can halt a specific room, even if the supply is 98% closed by value.

Claim — a separate accounting object

A claim should not disappear in a long project correspondence. It needs its own identifier:

CLAIM-ID
PROJECT
PURCHASE ORDER
SKU
QTY
ISSUE
PHOTO
DATE
STATUS
RESOLUTION

Statuses can be OPEN, SENT TO SUPPLIER, AGREED, REPLACEMENT IN PRODUCTION, CREDIT, CLOSED.

Linking to the original order helps to understand exactly what happened: damage during delivery, mispick, shortage, defect, or design error. These causes must not be mixed, because they require different corrections.

How to close a project after the last delivery

The final delivery does not mean the project is closed. Before archiving, the studio must bring the data into a state that will be useful a year later.

Worth saving:

• the final specification;
• actually installed SKUs;
• materials and finishes;
• stock and operational reserve;
• latest prices as historical data;
• supplier contacts;
• photos of key samples;
• closed claims and their resolutions;
• links to 3D/DWG;
• photos of completed assemblies.

This is how a completed project turns into a knowledge base, not just an archive of documents.

What to transfer from a completed project to the shared library

After closing, it is useful to hold a short retrospective. What has repeat value is transferred to the central catalog:

• reliable SKUs;
• approved samples;
• technical files;
• contacts and specifics of working with the supplier;
• actual notes on the profile or material;
• successful alternatives;
• information about compatible combinations.

But old prices, past availability, and historical lead times should not be turned into eternal truth. They remain in the project history with a date.

How a studio can work with the STAVROS assortment

A professional route can be built like this:

catalog → SKU → technical files → sample → project-spec → RFQ → commercial proposal → order → delivery.

The current STAVROS catalog includes moldings, wall panels, carved and stucco decor, furniture hardware, collections, and samples. For a studio, it is important not to copy the entire assortment into its own database, but to create a verified layer of the items it actually uses.

For panels, you can use the main wall panels category и Rafter panels. For stucco — polyurethane decor. For carved accents — Carved Decor.

If the project includes furniture elements, the following are separately available Furniture hardware и Wooden furniture handles. For an initial stylistic filter, you can use STAVROS collection.

Project card: what the studio should see before opening the specification

If the manager has to open dozens of rows every time to understand the status of an object, the portfolio is already overloaded with details. Each project should have a short project card — a top level from which you can drill down into the specification, budget, RFQ, and deliveries.

Minimum card fields:

• PROJECT ID and name;
• client;
• responsible interior fit-out specialist;
• lead designer;
• project address;
• current stage;
• planned installation date for key groups;
• approved budget;
• amount SELECTED / QUOTED / ORDERED / RECEIVED;
• the next three procurement deadlines;
• open risks;
• open claims.

The project card answers the question "what is happening with the project", not "what size is the molding". It does not duplicate the specification, but shows the state of the system. With ten projects, this is already critical.

Supplier register: store not only contacts, but also actual experience

A manager's contact and a website are too little for a multi-project studio. The supplier register should accumulate confirmed experience: which categories were actually purchased, how often deadlines changed, how convenient it is to receive samples, technical files, and repeat batches.

Useful fields:

• supplier / manufacturer;
• categories;
• contacts;
• sample request conditions;
• standard price request process;
• order history;
• average actual lead time for completed orders;
• claims and how they were resolved;
• notes on packaging and delivery;
• status ACTIVE / REVIEW / ARCHIVE.

This is not a "good / bad" rating. The goal is to store observed data. One supplier may handle samples and technical files excellently but have a longer production cycle; another may ship stock items quickly. For different tasks, this is a different profile.

Client approval must have its own record

The APPROVED status cannot be set just because the client wrote "like" under a photo. For purchasing, it is necessary to understand exactly what has been approved: SKU, material, size, finish, price, or only a visual idea.

Convenient to separate:

• DESIGN APPROVED — visual position approved;
• SAMPLE APPROVED — physical sample approved;
• PRICE APPROVED — client has agreed to the commercial cost;
• ORDER APPROVED — the order is authorized to be placed.

Not every project needs all four statuses, but mixing them is dangerous. A client may have approved a molding as a design, but not yet seen its price. Or the price is agreed, but the selected oak finish is not physically approved. The studio must see exactly which decision has been made.

For disputed or expensive items, it is useful to keep the date and source of approval: an email, meeting minutes, a note in the client portal. This protects both parties from a later “I approved a different option.”

How not to lose the budget between SELECTED and ORDERED

At an early stage, the specification contains estimated values. As the RFQ progresses, items receive actual project prices. If the studio does not separate these stages, the overall budget starts jumping without explanation.

A line item may have separate fields:

BUDGET ALLOWANCE
LATEST QUOTE
CLIENT APPROVED
ORDER VALUE
ACTUAL PAID

BUDGET ALLOWANCE — the limit or guideline set for a category. LATEST QUOTE — the most recently received price. CLIENT APPROVED — the commercially agreed amount. ORDER VALUE — the cost of the actually placed order. ACTUAL PAID — the actual payment made.

The difference between them is not an error but information. The manager can see where the project goes over budget before the order is placed. The design project specifier can propose an alternative or rebuild the category before the client's financial commitment.

Budget reserve and product reserve are different things

The word “reserve” in specification is used for two different entities. Financial reserve — money for changes, logistics, or unforeseen expenses. Product reserve — additional physical units for installation or future use.

They cannot be stored in a single percentage. For example, a project may have a financial contingency of 5%, but a specific skirting board according to the cutting map requires a different physical stock. For one-off decor, the reserve may be calculated in units, while for an expensive panel — through a specific additional modular unit.

If the client sees two clear fields, they understand why “money reserve” does not equal “extra product.”

Purchase order: the moment when a project line becomes a commitment

Before ORDERED, the data can still be changed relatively freely. Purchase order is the boundary. After it, any replacement may have cost, timeline, and legal consequences.

The PO must reference:

• PROJECT ID;
• RFQ / commercial proposal;
• the approved project-spec revision;
• specific SKUs and configurations;
• quantity;
• price;
• payment terms;
• readiness date;
• address or plan for future delivery.

You cannot create a purchase order from memory or reassemble it manually from several emails. It must be a logical continuation of the approved QUOTED state.

Payment status needs to be separated from production status

An order can be approved but not paid; partially paid; in production; ready. If all of this is combined into a single status of "in order," the procurement calendar ceases to be predictable.

It is useful to have two parallel fields:

PAYMENT: NOT INVOICED → INVOICED → PARTIALLY PAID → PAID.

FULFILLMENT: ORDERED → IN PRODUCTION → READY → SHIPPED → RECEIVED.

This way the manager immediately sees why production has not yet started: the supplier is delaying the launch or the invoice has not yet been paid. This is especially important when the client makes payments directly and the studio only coordinates.

How to handle partial deliveries of a single purchase order

A large order may arrive in parts. In that case, the RECEIVED status at the whole PO level is too coarse. Quantities per line are needed:

ORDERED QTY
READY QTY
SHIPPED QTY
RECEIVED QTY
CLAIM QTY
OUTSTANDING QTY

For example, 60 slats ordered, 60 ready, 40 shipped, 40 received, still

For wooden and MDF trim — a separate category; for panels — a separate one; for polyurethane and carved decor — their own. This reduces the risk that a "molding" made of different materials will be perceived as the same purchasing object.

If the studio regularly uses specific items, it makes sense to keep them in the central library marked VERIFIED. But before each new project, the interior specifier must re-check the commercial parameters, which may change.

When a new sample is needed, and when an existing one is sufficient

A sample can be reused if it relates to the same SKU, material, and relevant configuration. But if the project selects a different finish, a different species, or differs significantly in scale of application, the old sample may not be sufficient.

A new sample is needed especially often when:

• the product has changed material or execution;
• a new color or paint is important;
• the item becomes a key accent instead of a background one;
• the previous sample is damaged or visually outdated;
• the client requires physical confirmation of a specific batch.

The sample register should allow ordering a sample directly from the project-spec without creating a separate parallel table.

How not to turn the sample library into a free warehouse for client projects

The problem arises when dozens of samples remain with clients and at sites without a return deadline. After a few months, the studio buys duplicates of what already exists.

Four rules are enough for issuing a sample:

1. each sample has an owner — the studio or a specific client;
2. when issued, the location is recorded;
3. there is an expected return date or NON-RETURNABLE status;
4. once a week, a list of overdue samples is generated.

If the client pays for a sample and it remains their property, this must also be indicated. Then it disappears from the library's available stock and does not create a false promise for another project.

Weekly operating review of the procurement department

With multiple projects, it is useful to hold a short weekly review not of "what is generally happening," but of exceptions. Each project goes through the same questions:

• what needs to be approved this week;
• which RFQs are unanswered;
• which prices are expiring;
• which ORDER BYs are coming up in the next two weeks;
• which orders are delayed;
• which deliveries need to be scheduled;
• which complaints are open;
• which samples are overdue for return.

Such a meeting helps the department head manage the portfolio rather than discuss every line of every specification. Detail is opened only where there is risk.

Escalation: when the specifier should not solve the problem alone

Each risk must have a level beyond which the decision is escalated. For example:

• replacement of an approved SKU — designer / project manager;
• budget overrun above the agreed threshold — client / manager;
• missed deadline affecting installation — project manager;
• major complaint — procurement + manager;
• material change after the sample — designer + client.

If the specifier single-handedly "fixes" all problems, the system loses control over design, financial, and deadline decisions.

How to measure the work of the procurement department without meaningless KPIs

The number of emails sent or the number of lines in a specification says almost nothing about quality. It is more useful to measure process metrics:

• share of orders placed before ORDER BY;
• average response time to RFQ;
• number of replacements after APPROVED;
• share of deliveries with discrepancies;
• number of open claims older than the established deadline;
• share of samples with unknown location;
• share of items with an up-to-date master card;
• deviation of ORDER VALUE from the agreed budget.

These metrics help identify a process defect. For example, many late orders may indicate not poor performance by the purchaser, but rather client approval of samples happening too late. The data allows you to see the cause.

How to avoid duplicating an already published article about a single design project

The detailed logic of "visualization → real SKU → specification → quantity" is already covered in a separate piece about specifying a design project.

The current article starts at a different level. It assumes the studio knows how to furnish a single project, and answers the next question: how to ensure that ten such projects don't turn into ten incompatible accounting systems.

That is why here the master catalog matters more than the cutting of a specific molding, the sample register matters more than a single material board, and the portfolio dashboard matters more than a detailed schedule for one room.

How to avoid duplicating an article about a design studio's product range

Another adjacent topic is which samples and product groups an interior salon or design studio should have. It makes sense to explore it in more depth in a separate piece about the decor range for a design studio.

Here the subject is different. Even a perfect product library doesn't answer who took the sample, which price is current in PROJECT-B, when the quote expires, which RFQ is awaiting a response, and what needs to be shipped tomorrow. This operational part is what the current article covers.

How to control the validity period of a commercial proposal

The price may be correct on the day it is received and may no longer be valid by the time the client decides to place an order. Therefore, every QUOTED state must have a VALID UNTIL field or, if the supplier has not specified a term, a mandatory re-verification date.

A few days before expiration, the system should show the item in a separate list. The interior specifier decides whether to request a price extension, obtain a new quotation, or warn the client that the budget needs to be re-verified.

It is especially dangerous to store a quotation PDF without a link to the project-spec. A month later, an employee sees a nice final total and transfers it to the budget without noticing that the quantity and material have changed since then.

How to avoid ordering the same item twice

With multiple projects, duplicates arise not only between sites but also within a single one. One employee sent an order by email, another later saw the APPROVED status and decided that a purchase order had not yet been created.

The safeguard is a unique PO ID and an atomic status transition: a line can become ORDERED only if it has a link to a specific purchase order. ORDERED cannot be set manually without a supporting document.

Before issuing a new PO, the system checks whether there is already an open order for the same PROJECT + SKU + CONFIGURATION. If there is, the employee must choose: is this an additional order or a duplicate.

For an additional order, a separate line is created with a reason: ADDITIONAL QTY, DAMAGE, DESIGN CHANGE, or SHORTAGE. This way, analytics does not mix repeat demand with the original one.

How to close a purchase order based on actual receipt rather than the invoice

An order should not be considered CLOSED just because it has been fully paid. Financial closure and operational closure are different events.

A PO can be closed when:

• all ordered items are received or cancelled by agreement;
• all discrepancies are recorded;
• claims are closed or moved to a separate controlled process;
• documents are received;
• the supplier's remaining obligations equal zero;
• the actual cost is reflected in the project budget.

If one item out of twenty is awaiting replacement, the entire order may have the status PARTIALLY CLOSED, while the problematic line is CLAIM OPEN. This way the project does not stall entirely because of one part, but the issue does not disappear from control.

Finishing materials supplier: what a studio really needs from communication

For a multi-project studio, a good finishing materials supplier is valuable not only for its range. Data predictability matters: clear SKUs, up-to-date product pages, the ability to get samples, technical materials, a commercial proposal, and an unambiguous order status.

When a studio wants to request the cost of materials, the request should arrive already structured. It is easier for the supplier to confirm the price and lead time for a specific configuration than to decipher renders and text messages.

This kind of communication benefits both parties: the manager calculates the RFQ faster, and the studio receives data that can be entered into the system without manual retelling.

Project procurement of finishing materials: where design ends and operations begin

Procurement of finishing materials does not begin with payment. Its starting point is when a project item becomes sufficiently defined to pass through the commercial cycle. Before that, it is in SELECTED or APPROVED status, but is not yet an order.

Operational cycle:

APPROVED → RFQ → QUOTED → CLIENT APPROVED → ORDERED → PRODUCTION → READY → SHIPPED → RECEIVED → CLOSED

Design can continue to exist in its own documents, but the procurement system should receive only controlled changes. If a designer changed a molding after ORDERED, that is already a change request, not "updated the render."

How to create a request for STAVROS from the studio's internal system

Before contacting STAVROS, it is useful to generate an export containing only its product items. It does not need products from other suppliers, client comments, or the studio's internal financial calculations.

The export may contain:

• PROJECT ID;
• internal item code;
• STAVROS SKU;
• the material;
• size;
• quantity;
• the required date;
• a question about the sample;
• delivery city;
• a comment on the batch.

If a commercial proposal needs to be obtained, such a form is much stronger than a set of screenshots. After receiving a response, the data returns to the price history and RFQ rather than remaining a separate email.

How to distribute responsibility within the procurement department

Even a small studio benefits from separating types of responsibility. One person can perform several roles, but the data should show who is responsible for what.

In a small team, a single design project procurement specialist can handle both procurement and logistics. But even then, the OWNER fields help clarify who currently holds the next action.

WIP limit: why it's harmful for a procurement specialist to hold too many "hot" items at once

If an employee is simultaneously handling dozens of urgent approvals, RFQs, and claims, the work becomes reactive. It's useful to distinguish between the total portfolio volume and the active WIP — items requiring action today.

The dashboard should show not a thousand rows, but specific queues: WAITING CLIENT, WAITING SUPPLIER, ACTION TODAY, OVERDUE. Then the procurement specialist doesn't have to scan the entire project looking for what's "on fire."

If the ACTION TODAY queue consistently exceeds the team's working capacity, the problem is systemic: RFQs are launched too late, there are no SLAs, or one employee is handling too many projects.

Internal studio SLAs: how long an item can wait

For key transitions, internal targets can be set. For example, an RFQ should be sent within one business day after APPROVED, an incoming quote should be entered into the system the same day, and a claim should be registered immediately after the fact is confirmed.

These are not universal standards or supplier promises. This is the studio's internal discipline. It helps separate external delays from your own.

If the supplier responds in five days, that's external lead time. If their response sits in the inbox for two days and no one updated QUOTED, that's already internal lost time.

How to manage multiple addresses and phases of a single project

A single project may have more than one address or more than one phase. For example, first the showroom is furnished, then the office; or one site includes several buildings. The Project ID remains shared, but shipment destination and phase must be separate fields.

A convenient notation:

PROJECT-A / PHASE-01 / ADDRESS-01
PROJECT-A / PHASE-02 / ADDRESS-01
PROJECT-A / PHASE-03 / ADDRESS-02

This prevents the error where goods for the correct project go to the wrong site or too early into the next phase.

How to manage client-supplied and studio-procured items

Not all goods are necessarily purchased by the studio. Sometimes the client pays the supplier directly, sometimes procurement is handled by the general contractor. But if the item affects the design and timeline, it should still be visible in the overall specification.

Add a PROCUREMENT OWNER field:

• STUDIO;
• CLIENT;
• CONTRACTOR;
• OTHER.

Then the studio doesn't confuse "we don't purchase" with "we don't need to monitor." A client item can have the status ORDERED BY CLIENT and still participate in the procurement calendar.

What to do if the client asks to order interior furnishing, but the project isn't ready yet

The phrase "order interior procurement" may sound like the start of purchasing, even though the design is still changing. A professional studio first determines readiness: which categories are approved, which dimensions are confirmed, which samples are required, and where the risks are.

If the project is not ready, the service can begin with setup: a central specification, data collection, building a library, initial RFQs, and a procurement calendar. But placing orders for undefined items is premature.

This is more honest than creating the appearance of activity through early purchases that will later have to be changed.

When a studio doesn't need a complex system and where to start with the minimum

Not every team needs a heavy software framework right away. If a designer handles one or two small projects and purchases a limited number of items, a full-fledged database with dozens of statuses can create more work than it saves. What matters is not the scale of the tool, but preserving the basic principles.

The minimal version can consist of just four registers: PRODUCTS, PROJECTS, SAMPLES, and ORDERS. PRODUCTS stores one card per SKU. PROJECTS — the selection of items and quantity per site. SAMPLES — the physical location of samples. ORDERS — RFQ, price, purchase order, and delivery status. Even a regular spreadsheet will do, as long as data is not duplicated and each entity has a unique ID.

Systematic interior procurement does not require complex software from day one. The system should become more complex based on actual pain. If employees regularly use outdated prices — price history is added. If samples get lost — a sample register with returns appears. If shipments get mixed up — project code and shipment card are introduced. If the manager cannot see deadlines — an exceptions dashboard is created.

There is no need to implement ten statuses just because they are listed in the article. If the team genuinely distinguishes SELECTED, APPROVED, ORDERED, READY, RECEIVED, and CLOSED — that may be enough. A new status appears when a separate management task regularly arises between two existing states.

For a small team, interior procurement is already considered manageable if the basic data is reproducible by another employee. The main maturity test is simple: another employee should be able to open the project and, without verbal explanation, understand which item is selected, where the sample is, which price is current, what the client has approved, what has been ordered, and when delivery is expected. If this is possible — the system works, even if it is not built in specialized software.

FAQ: how an interior procurement studio works

What does an interior furnishing studio do?

It organizes the transition from selected design decisions to managed procurement: it maintains the specification, samples, supplier requests, commercial proposals, approvals, purchase orders, delivery timelines, and closing of items. The specific scope of the service depends on the studio's contract.

How does a furnishing specialist differ from a designer?

The designer is primarily responsible for the design and visual solution. The interior furnishing specialist translates the selected decisions into product and procurement data, and controls commercial proposals, timelines, and deliveries. In a small studio, these roles may be performed by one person, but the functions remain different.

Who is a design project furnishing specialist?

This is a specialist who works with real products within a design project: SKUs, materials, samples, prices, suppliers, orders, and logistics. When there are multiple projects, a design project furnishing specialist must manage not only each specification but also shared reference data and portfolio statuses.

What is included in the interior furnishing service?

Usually this includes selection and verification of products, maintaining the specification, organizing samples, RFQs, comparison of commercial proposals, approvals with the client, purchasing, and delivery control. The specific list is fixed by the contract; one should not assume that any studio automatically includes acceptance, storage, or payment on its own behalf.

How to calculate the cost of furnishing a design project?

The cost of the studio's service must be separated from the cost of goods, delivery, and additional expenses. The specific payment model for the service may be fixed, staged, or another — it is determined by the studio itself. The product budget is calculated based on real SKUs and current commercial proposals.

How can studios manage multiple projects at the same time?

Use a central product catalog, separate project specs, unified statuses, a sample register, price history, RFQs with revisions, and an exceptions dashboard. The same SKU is stored once in the central database, but its project configurations and prices remain separate.

How should a sample library be organized?

Assign each physical sample a sample ID, link it to the SKU and digital master card, and record its location, owner, project, and return date. It is useful to have the statuses IN LIBRARY, WITH CLIENT, ON SITE, RETURN EXPECTED, and ARCHIVE.

How should current supplier prices be stored?

Do not store a single number without a date. Each price must be linked to a date, source, project, quantity, and configuration. Price history is retained, but the data is rechecked before a new order.

How should a request to a supplier be drafted?

Provide the project code, RFQ revision, SKU, material, size, quantity, required date, address, and questions about availability and samples. The more precise the request, the fewer manual clarifications and the lower the risk of receiving a quote for a different configuration.

How should procurement deadlines be tracked?

For each item, store SELECT BY, APPROVE BY, ORDER BY, and NEED ON SITE. Calculate the order date backward from the required installation date, taking into account production, delivery, and approval.

How to handle claims?

Create a separate CLAIM-ID, link it to the project, PO and SKU, record the quantity, issue, photos, date and resolution status. The claim must remain visible until closed.

Where should a designer order finishing materials and decor?

For STAVROS products, a designer or studio can work with the official catalog, professional technical materials and samples. A specific SKU is transferred into the project system, not just an image or category name.

Can the same STAVROS price be used across all projects?

No. A historical price can serve as a reference, but the current cost depends on the date, configuration and terms of a specific order. Before an RFQ and purchase order, the price must be confirmed again.

Should closed projects be kept?

Yes, but as an archive and knowledge base. From them, it is useful to transfer verified SKUs, samples, technical files and actual notes into the central library. Prices and lead times remain historical rather than automatically current.

Final operating scheme of the studio

When there are many projects, interior furnishing turns from a set of personal habits into a system. It can be reduced to several stable levels:

1. Portfolio. List of projects, owners, stages, budgets, and upcoming deadlines.
2. Master catalog. One card per real SKU and product configurations.
3. Project-spec. Only the items that belong to a specific object.
4. Sample register. Tracking of physical samples and their locations.
5. Price history. Price always with date, project, and source.
6. RFQ / quote. Versioned request and structured commercial proposal.
7. Approval. Separate confirmation of design, sample, price, and order.
8. Purchase order. Fixed commitment to a specific revision.
9. Fulfillment. Production, readiness, shipment, acceptance.
10. Claim. Separate track for discrepancies and claims.
11. Closeout. Final actual specification and transfer of knowledge to the shared library.

STAVROS occupies a clear place in this scheme: it supplies real product items and data on them. The studio selects the required categories in catalog, uses technical files, orders samples, generates RFQs, receives an up-to-date quote, and links the order to its project code.

At the same time, each individual object retains its own logic: interior furnishing is handled in the project-spec, while shared knowledge remains in the master catalog. The main difference between a professional system and a set of spreadsheets is unambiguity. One product has one master card. One sample has one location. One price has a date. One RFQ has a revision. One order has a basis. One claim has a status. Then, even with twenty simultaneous projects, the team does not mix products, money, and obligations between clients.