CHAPTER 4
REQUEST FORM
In the first chapter of this training, we introduced the 5 request types. One of the elements mentioned was "Output from Vendor". But receiving the desired output, obviously also requires sending over the necessary input. And that's what this chapter is about:
🙌 How to create a request! 🎁
4.1 - PDF TEMPLATE 📝
There's a number of different elements required for sending out a request. Some of them apply to all of the 5 different request types, others are only necessary to half of them. In this subchapter we'll explain all those differences and what you should pay attention to when preparing your requests.
We've created an interactive PDF request form which you can use as a template for your requests. It includes all the information and files your vendor will need for each request type. So we recommend to use this form as a checklist, to make sure your request is complete! You can access the template on the Vendor Hub, as introduced in Chapter 1.
☑️ Use this request form as a checklist to make sure your request is complete!
👇 Find a preview of the form below 👇
Hover over the different elements for brief explanations on each category.
Underneath the preview is a full explanation for each element.
Fill out the checklist under the request type selected in step #2
Hover over the images to see brief explanations of each element
Brief Basics ✏️
Style Number
Request Type
Request Date
Deadline
Avatar Reference*
Pattern Reference*
Fill in style number or PLM code here
Select the type of request you're sending out
Select the date of sending out the request
Select the deadline by which you need the file
(keep in mind the average turnaround time from Chapter 1!)
Select which ABP avatar from your brand should be used.
(ABP = Alvanon Body Platform, click here for more info)
Fill in a block or pattern name which can be used as a
base/reference to create a block or style from scratch
* Only applicable to New Style & Block requests.
Crucial Checklists ✅
Input Checklist
Required Input
Optional Input
All the files & information required for each type of request.
You only need the column underneath the request type you selected in Section . Use it as a checklist to make sure you include all the required fields, and decide for yourself which of the optional fields are necessary for your request.
Make sure to always include these files with your request!
(Only those underneath the request selected in Section )
Choose which of these files are applicable to your request.
(Only those underneath the request selected in Section )
Optional Others 💭
Preferences
Additional comments
Stylezone Standards
Use this area to communicate your preferences regarding smart trims. Smart trims are used by default, so you only need to change this if you don't want smart trims. If you're thinking "But WHAT is a smart trim? 🧐" - no worries! We'll explain all about it in Chapter 6!
Blank text field for any extra comments about the request. For example any wishes regarding the styling of the garment: hood up/down or a garment opened up to show inside detailing (think of outerwear or a shirt's cuff).
Preference for different upload settings? Change it here!
4.2 COMPLETED FORM (EXAMPLE) ☝️
After all of this information about the different fields, options & what's important to pay attention to, there's one thing left to do for this subchapter... An example! So below you can find a completed form, which is filled in for a block request. An imaginary one of course, it's just an example! 😉
Click on the image to view it in full-size, or download the .PDF to check out the file itself.
REQUEST TYPE,
REQUEST DATE
& DEADLINE
AVATAR REFERENCE
INPUT CHECKLIST
REQUIRED INPUT
OPTIONAL INPUT
The average estimated turnaround time for a block request is 2 days, so the time span between the request date & the deadline is achievable for the vendor.
If you work for CK: either leave the field of the TH avatar reference blank, or fill in "not applicable" (and vice versa if you work for TH)
Because this form belongs to a block request: the other 4 input checklists (of the other request types) can be ignored/left blank.
The request form was sent out with the required input: the block/pattern reference was filled in, and a sketch was shared with the vendor.
The Size spec was already created by the time the request was sent out, which is why it was also already included with the request.
However, the BOM and Techpack weren't finished yet, that's why they couldn't be shared with the vendor yet for this request.
This block was stitched up with basic fabrics and trims from the standard libraries, which is why it was not necessary to include any specific fabrics or trims with this request.
Using the request form is not mandatory, that's all up to you! However, we do
strongly recommend to fill in this request form for each request you send out.
💡
HALFWAY THERE! 🔥
We're halfway through the phase of creating a request, and at the same time
we're also about halfway through this complete training... Getting there! 🙌