An RFC is a formal way to let us know about any factual issues or misalignments in your delivered assets. It ensures we can track, resolve, and rework the affected products — efficiently and with full context.
We always aim to minimize the need for RFCs by setting clear expectations in advance to the production start. That includes aligning on how we operate, what you can expect from a typical delivery, and collecting potential brand-specific styling preferences early on. A good way to prepare is by reading Fibbl’s User Manual, which explains our production process, visual standards, and the limitations of 3D workflows in detail.
RFCs are not for subjective tweaks or personal preferences — they’re for concrete issues that need correcting to ensure your product is faithfully represented.
What qualifies for an RFC?
You can submit an RFC if:
The 3D model deviates from the real physical product
Key details (like logos, materials, or components) are missing
The shape, symmetry, or styling is incorrect compared to the agreed style guides
Something important was agreed upon during pre-production but is not reflected in the output
⚠️ RFCs are not meant for subjective feedback or creative preferences (e.g. “we want a warmer tone in the leather”, or “can you make the suede more red?”).
How it works
Wait for the full batch to be delivered
We process feedback in bulk, at once. Please hold off until the entire batch of assets is delivered before submitting feedback.
Review your delivery carefully
Take time to review all assets. When comparing, remember that one product can be perceived differently under a yellow office light compared to a white-balanced photo studio. Thus, the point of reference must be the reference photos of the physical product in the Fibbl studio (found on the model detail page under the option Render settings).
Identify deviations
Note anything that’s factually incorrect — e.g., a wrong logo, misaligned stitching, or inconsistent shape compared to the agreed style guide.
Fill in the RFC template
Use our RFC template (Google Slide) to report the affected products. Be as clear and specific as possible.
Submit within 7 days
Send your RFC within 7 working days of receiving the full batch to your Customer Success Manager. This helps us stay on top of production and quality assurance.
We review & confirm
Our team will review the request and confirm which items will be reworked. Approved RFCs go into a new correction batch which will get a separate timeline.
Reworked assets delivered
Once done, you’ll be notified. Updated versions will appear automatically in the Fibbl platform.
More questions?
Reach out to your Customer Success Manager and they'll help you out.